-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Declare support for Python 3.13 #2071
base: master
Are you sure you want to change the base?
Conversation
85dca33
to
49c23b9
Compare
Tests are 🟢 over on my fork: https://github.com/edgarrmondragon/faker/actions/runs/9849708765 |
.github/workflows/ci.yml
Outdated
@@ -154,6 +160,7 @@ jobs: | |||
uses: actions/setup-python@v5 | |||
with: | |||
python-version: ${{ matrix.python }} | |||
allow-prereleases: true |
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.
Why not using "3.13-dev"
instead to better indicate that Python 3.13 is not yet available as a stable release?
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.
Feels easier to let it stay as 3.13
after the final release rather than coming back and changing it from 3.13-dev
to 3.13
. I don't have a strong preference, though.
Rebased and confirmed with |
cb9e384
to
c2a3da3
Compare
What does this change
The first release candidate of Python 3.13 is around the corner (2024-07-30), this adds it to the test matrix and declares support in the project metadata.
What was wrong
Python 3.13 seems to be supported without any code changes, but this makes sure it's tested.
How this fixes it
3.13
to the list of versions foractions/setup-python