-
-
Notifications
You must be signed in to change notification settings - Fork 628
CI: advance the Python version support window #2246
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
Closed
jayaddison
wants to merge
5
commits into
jazzband:main
from
openculinary:issue-2138/advance-py-support-window
+5
−3
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7a29213
CI: advance the Python version support window
jayaddison 30519e4
CI: add Python3.13 to GitHub Actions `cron` workflows
jayaddison eb306c1
Packaging: add Python3.13 to PyPi classifiers
jayaddison e9feb94
Packaging: remove Python3.8 (near EOL) from PyPi classifiers
jayaddison ef8b749
Changelog: add changeset description (adds py3.13, removes py3.8)
jayaddison File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
Test and declare Python 3.13 support in `pip-tools`; remove support for Python 3.8 | ||
-- by {user}`jayaddison` (for OpenCulinary). |
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
Oops, something went wrong.
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.
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.
This mustn't be in a section with random unimportant changes. There's a removal and addition of support. There's respective sections for both.
Although, I don't think we're in rush to drop 3.8 right away. Is it causing problems?
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.
Ok; would it be preferable to isolate this into two changesets, one to add Python3.13 as a
feature
change note, and then potentially a Python3.8deprecation
?I'm not aware of any problems due to Python3.8 here, nope - my main motivation was to maintain a similar level of CI resource usage/cost, despite exercising an extra Python version.
In fact: I also note that I omitted to update the
requires-python
directive in thepyproject.toml
here; so in fact this changeset does not entirely remove Py3.8 support, as it stands.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 would treat two PRs as preferable, yes.
Adding and removing versions touches different metadata, e.g.,
Requires-Python
when the lower bound moves.Upon reflection, I don't think we're ready to drop 3.8 quite yet. This is open to debate, but I'd like to do one more bugfix release before removing a version (even an EOL one; lots of orgs move versions slowly).
Once we don't support 3.8, a series of small cleanups come into play, e.g., the
black
andpyupgrade
version numbers. I think I prefer to do those separately from the version bump as well, which I would confine to package metadata and CI configuration.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.
Thanks, @sirosen - I'll close this and re-open a more narrowly-focused pull request that adds py3.13 without removing py3.8 support.