-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
drop python 3.7 support, drop pypy3.7-3.8, add pypy3.10 (except on windows) #2668
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2668 +/- ##
==========================================
+ Coverage 98.84% 98.88% +0.04%
==========================================
Files 113 113
Lines 16508 16482 -26
Branches 3010 3000 -10
==========================================
- Hits 16317 16299 -18
+ Misses 134 126 -8
Partials 57 57
|
Hi, if I actually am able to release stuff I want to do a patch release with current changes (and without this PR), then soon after a minor release with this PR. This way there's a published version of trio that supports 3.7-3.12 (beta, at least). Sorry it took me a while to figure that out, but that means this PR will have to wait a bit! |
That sounds like a good approach, no worries at all! |
We can probably https://github.com/python-trio/trio/blob/master/trio/_util.py#L268-L290 |
I have no clue what the |
Hmm, I'm failing to find a way to get both runtime and static checking to work with a single decorator/metaclass (it seems mypy checks for |
Dropping windows pypy3.10, leaving that for another PR. |
@A5rocks wanna review/merge? |
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.
Looks mostly good. Please edit pyproject.toml
to make black
use py38
as a minimum version. I don't think it changes anything though.
Sorry about the delay in reviewing! ... I swear I had another thing in mind to ask you to change but whatever, we'll catch it eventually and it won't break anything.
@@ -66,7 +66,7 @@ jobs: | |||
# support this for PyPy presently so we get no help there. |
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.
note to self: test if this is supported yet. It probably works!
@@ -143,7 +143,7 @@ jobs: | |||
strategy: | |||
fail-fast: false | |||
matrix: | |||
python: ['3.7', '3.8', '3.9', '3.10', 'pypy-3.8-nightly', 'pypy-3.9-nightly'] | |||
python: ['3.8', '3.9', '3.10', 'pypy-3.9-nightly', 'pypy-3.10-nightly'] |
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.
Mind adding at least pypy 3.10 here?
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.
In addition to pypy-3.10-nightly
? Ubuntu tests both pypy-3.10
and pypy-3.10-nightly
, windows & mac has always only tested pypy-nightlies (no clue why they do that instead of the stable releases though)
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.
Just remembered the one more thing: can you make a news fragment?
newsfragments/2668.headline.rst
Outdated
@@ -0,0 +1 @@ | |||
Drop support for python3.7, pypy3.7 and pypy3.8. |
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.
should be Python 3.7 and PyPy 3.7/3.8
or similar.
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 seems fine now.
Except for capitalization in the newsfragment, I suppose.
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.
Sorry, I've been thinking about it and IMO this isn't really a "headline" feature; in the past this was a .removal
.
That plus the capitalization thing are my only concerns, after which feel free to merge!
Oh, I missed that capitalization was what Fuyukai actually was requesting be modified. Thanks for clarifying :) |
|
With 3.7 EOL coming up in 4 days, I thought it time to start writing a PR for dropping it so #2655 can move ahead afterwards.
Only thing I stumbled on so far (until CI tells me otherwise) was
trio/_util:coroutine_or_error
- which seems to be more than an easy search/replace fix.