-
Notifications
You must be signed in to change notification settings - Fork 45
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
Python 3.13 support #158
Python 3.13 support #158
Conversation
Python 2 is no longer supported in Ubuntu docker image
34a9dff
to
4ae02e1
Compare
4ae02e1
to
08f4a50
Compare
@@ -27,7 +31,7 @@ jobs: | |||
docker: | |||
- image: circleci/python:3.4 | |||
|
|||
test: | |||
test_old_pythons: |
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.
These versions of Python don't have access to setuptools==71.1.0
, so were implicitly pinned at older versions already.
You maybe would want to remove some old Python version classifiers from setup.py as well. |
@squeaky-pl We still support all those versions though (at least, we've kept all the edge-case handling for them in the code). #157 is the ticket for capturing the drag of old versions. |
What are you trying to accomplish?
#155
Adding support for Python 3.13
What approach did you choose and why?
I added 3.13 everywhere.
I had to adjust some calls to
exec
as a result of thelocals
changes that happened in 3.13.Otherwise the imports wouldn't result in changes to the
globals
, so subsequent calls wouldn't see the libraries as imported.I also had to pin the version of
setuptools
to an old version, since they dropped support for being used as a test runner in v72 (#147).What should reviewers focus on?
🤷, once this is merged, I'll rebase #154, and we should be able to get 2.3.2 released 🤞.
The impact of these changes
We'll have Python 3.13 in our tests and our builds.