-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
Upgrade Python 3.13 to beta 1. #2407
Conversation
@@ -17,7 +17,7 @@ PYENV_VERSIONS=( | |||
3.9.19 | |||
3.10.14 | |||
3.12.3 | |||
3.13.0a6 | |||
3.13.0b1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An item of note: this is the 1st Python release to support ZIP64 in zipimporter: aka Python 3.13 PEXes can now contain huge ML apps without --layout {loose,packed}
shenanigans being necessary.
# Git is needed for the git VCS URL the patched Pip needed for Python 3.13 | ||
# pre-releases is resolved by. | ||
# TODO(John sirois): Remove once a Pip with Python 3.13 support is released: | ||
# https://github.com/pex-tool/pex/issues/2406 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I happened to notice that pip has done a 24.1b1 release which seems to include pypa/pip#12462. Doesn't have to be this PR, but could PEX switch over to using that one for validating 3.13 rather than the git version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps, but it would, like the git version, be temporary and never public. I don't ever intend to add anything but production Pip versions to the --pip-version
enum.
No description provided.