Closed bdraco closed 1 month ago
Attention: Patch coverage is 89.47368%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 88.07%. Comparing base (
d6e71b6
) to head (c6a2845
). Report is 2 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
src/propcache/_helpers_py.py | 60.00% | 0 Missing and 2 partials :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
pre-commit config needs to be updated. Also, should we go top-down and drop 3.8 from aiohttp first? Currently, its changelog only mentions the drop in
master
/ v4. Should 3.11 be released first?
Probably a good idea. I was waiting for digest auth / middle ware to land in 3.11 before releasing but no reason we can't release 3.11 tomorrow and land it in 3.12
pre-commit config needs to be updated. Also, should we go top-down and drop 3.8 from aiohttp first? Currently, its changelog only mentions the drop in
master
/ v4. Should 3.11 be released first?Probably a good idea. I was waiting for digest auth / middle ware to land in 3.11 before releasing but no reason we can't release 3.11 tomorrow and land it in 3.12
I think we should wait a little longer before releasing 3.11. I see no reason to block this on the aiohttp release though. FYI, if you look at https://pypistats.org/packages/aiohttp Python 3.8 is still the second most popular version most days. So, it'd be nice to keep the 3.10 release going till atleast the end of the year.
Okay, let's not block, then.
What do these changes do?
Drop Python 3.8 support
3.8 has reached EOL as of the 7th of October https://devguide.python.org/versions/
Are there changes in behavior for the user?
Drop Python 3.8 support