Skip to content

Maintenance: Add support for Python 3.12 #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Maintenance: Add support for Python 3.12 #712

merged 1 commit into from
Apr 22, 2025

Conversation

amotl
Copy link
Member

@amotl amotl commented Feb 11, 2025

About

Make the operator support Python 3.12.

Blocked by

@amotl amotl force-pushed the python312 branch 3 times, most recently from 4a93570 to dcc4ea1 Compare February 11, 2025 20:35
@amotl amotl requested review from juanpardo and tomach February 11, 2025 20:47
@amotl amotl marked this pull request as ready for review February 11, 2025 20:47
@amotl amotl requested review from plaharanne and removed request for juanpardo February 14, 2025 10:18
@amotl amotl force-pushed the collab/modernize branch 4 times, most recently from 8d50802 to de87095 Compare February 19, 2025 18:57
@amotl amotl force-pushed the python312 branch 2 times, most recently from d5fdb02 to b46f806 Compare February 19, 2025 19:02
Comment on lines +530 to +535
node_index = int(next_pod_name[next_pod_name.rindex("-") + 1 :])
node_progress = f"{node_index + 1}/{len(all_pod_uids)}"
await send_operation_progress_notification(
namespace=namespace,
name=name,
message="Waiting for node "
f"{int(next_pod_name[next_pod_name.rindex('-')+1:])+1}/{len(all_pod_uids)}"
" to be restarted...",
message=f"Waiting for node {node_progress} to be restarted.",
Copy link
Member Author

@amotl amotl Feb 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This update is just because of line length limitations, now raised by the flake8 linter, after updating it.

Cutting the statements in the middle of the string interpolation feels nasty, so we did it this way, separating the statements from each other.

Base automatically changed from collab/modernize to master March 3, 2025 20:03
@amotl
Copy link
Member Author

amotl commented Mar 3, 2025

After merging the other one, I've just also refreshed this patch. Compared to GH-549, it touches a bit of the code, but it is still pretty trivial. @tomach: Can you have a look? 🙏

Updating the runtime image is an orthogonal concern, so I've created a dedicated ticket about it.

@amotl

This comment was marked as outdated.

@tomach tomach marked this pull request as draft March 31, 2025 07:03
@amotl
Copy link
Member Author

amotl commented Apr 14, 2025

I've just refreshed the patch. 🍀

@amotl amotl marked this pull request as ready for review April 14, 2025 14:53
@plaharanne
Copy link
Contributor

plaharanne commented Apr 22, 2025

it looks good to me, but I'll let @tomach have the last word (because he is more aware of that topic than me).

@plaharanne plaharanne removed their request for review April 22, 2025 08:03
@tomach
Copy link
Contributor

tomach commented Apr 22, 2025

it looks good to me, but I'll let @tomach have the last word (because he is more aware of that topic than me).

LGTM! doesn't seem to have any behavioral changes.

@amotl amotl merged commit 27498a5 into master Apr 22, 2025
11 checks passed
@amotl amotl deleted the python312 branch April 22, 2025 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants