Skip to content
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

Bump Python to 3.12.3 for rolling #69

Closed
wants to merge 1 commit into from
Closed

Conversation

mikaelarguedas
Copy link

@mikaelarguedas mikaelarguedas commented May 7, 2024

chocolatey ships python3 3.12.3 and minimum requirement for Jazzy is Python 3.9

This PR suggests bumping python to 3.12.3 for rolling and then see to apply it to Jazzy.

TBH I don't know how this part of the infrastructure works and if there are discussion and work in that direction already ongoing 😅

The initial motivation is because CI fails on Windows when Python 3.9 features are used: ros2/sros2#300 (comment)


Once the approach validated: I can open the related PRs to REP-2000 and ros2/ci

@clalancette
Copy link
Contributor

chocolatey ships python3 3.12.3 and minimum requirement for Jazzy is Python 3.9

So unfortunately, as much as I would like to, we cannot upgrade Python beyond 3.8 on Windows at this time.

The problem is complicated, but it boils down to the fact that Qt stopped providing Windows installation binaries after Qt 5.12.10. Since there are no installation binaries, there is no way we can install Qt on Windows for RViz and RQt.

The fallout from that is that Qt 5.12.10 also forces us to stay on Python 3.8. You can see some of the work that @sloretz attempted to do to fix this for Humble in #44 .

The long-term plan is to switch to conda for all of this, which will alleviate all of the problems (they rebuild Qt, so we can just use that). But that isn't going to happen for Jazzy.

My suggestion here is that we close this PR and instead update REP-2000 to say Python 3.8.

@clalancette
Copy link
Contributor

And see ros-infrastructure/rep#404 for an update to REP-2000.

@mikaelarguedas
Copy link
Author

wow that's very unfortunate, same version as Noetic.

Is the plan forward laid out somewhere ? maybe people can contribute to help move this forward

@mikaelarguedas mikaelarguedas deleted the choco_python3 branch May 7, 2024 13:26
@clalancette
Copy link
Contributor

Is the plan forward laid out somewhere ? maybe people can contribute to help move this forward

I haven't opened an issue about it, no. It's one of the things I want to address as soon as we get Jazzy out the door, as the current situation has become untenable.

@mikaelarguedas
Copy link
Author

I haven't opened an issue about it, no. It's one of the things I want to address as soon as we get Jazzy out the door, as the current situation has become untenable.

👍 thanks for all the info

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.

2 participants