Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
gh-118830: Bump DEFAULT_PROTOCOL to 5 (#118830)#119340
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
mdkcore0 commentedMay 21, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
On a second thought it makes sense to add it, but in which section this change falls in? |
Yes, this deserves a NEWS entry, and it should go in |
This not only deserves a change log entry but also a "What's New in Python 3.14" entry. |
@carljm,@ambv: I've added requested entries For the "WhatsNew in 3.14" I looked on how it was added for python 3.8 (the rst file), it includes some wording about the impact on performance (under Optimizations section):
Is it a good idea to add something like that here? Since I'm starting contributing now, I will need some help to fulfill it :) |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
b65e9fb to70676b2CompareBefore bumping it to version 5, I would like to address#120380 since it could introduce breakage. At least, there was something that was not correctly handled for pickle's buffers. |
mdkcore0 commentedJun 18, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
no problem, thanks!! |
picnixz commentedJun 27, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Now that#120380 is fixed, I think this can be done, unless someone finds something that is broken for protocol 5 or something that should be supported for protocol 5 and that is not. There are#84895 and#89467 which could be something that is desired before bumping the default protocol to protocol 5 since they could dramatically improve performances (especially the second one). |
I don't think either of those needs to block this PR. I've resolved the conflict in the What's New document, and in the process moved the entry fromOptimizations toImproved Modules. Unlike version 4, version 5 isn't primarily a performance improvement. |
Uh oh!
There was an error while loading.Please reload this page.
See also thefailed CI check:
|
oh, cool |
Yes please! |
Thank you! |
Uh oh!
There was an error while loading.Please reload this page.
I didn't have add a news entry, as it is not a user facing change. Should do I add it?
📚 Documentation preview 📚:https://cpython-previews--119340.org.readthedocs.build/