Migration to python 3.13 #87
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Arapak
force-pushed
the
migrate-to-py13
branch
from
ee6e03f to
4538b90
Compare
Arapak
force-pushed
the
migrate-to-py13
branch
from
4538b90 to
24d3b99
Compare
Member
|
Why did I get assigned as reviewer for this one and not @twalen ? 🤔 |
Wolf480pl
reviewed
Dec 10, 2025
Member
Wolf480pl
left a comment
Wolf480pl
left a comment
There was a problem hiding this comment.
I'm quite out of the loop with sio, and not really sure if this update to 3.13 is correct.
If @twalen is unable to approve it for some reason (eg. CODEOWNERS behaving in a weird way), I can click the "approve" button, but don't count this as a proper review.
Contributor
I'm on this PR. The email about review was automatically generated by github since you are in CODEOWNERS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated filetracker’s Python version from 3.8 to 3.13. Upgrading Gunicorn from 19.9.0 to 23.0.0 required adjusting the logging configuration, as outlined here: benoitc/gunicorn#2250
Gunicorn commit that introduced the logging change:
benoitc/gunicorn@6da84c6