Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Merged
encukou merged 4 commits intopython:mainfrommdkcore0:gh-118830
Jul 19, 2024

Conversation

@mdkcore0
Copy link
Contributor

@mdkcore0mdkcore0 commentedMay 21, 2024
edited by github-actionsbot
Loading

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/

@bedevere-app
Copy link

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 theskip news label instead.

@mdkcore0
Copy link
ContributorAuthor

mdkcore0 commentedMay 21, 2024
edited
Loading

On a second thought it makes sense to add it, but in which section this change falls in?

carljm reacted with thumbs up emoji

@carljm
Copy link
Member

Yes, this deserves a NEWS entry, and it should go inLibrary section, I think.

ambv and mdkcore0 reacted with thumbs up emoji

@ambv
Copy link
Contributor

This not only deserves a change log entry but also a "What's New in Python 3.14" entry.

mdkcore0 reacted with thumbs up emoji

@mdkcore0
Copy link
ContributorAuthor

@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):

  • The default protocol in the :mod:pickle module is now Protocol 4,
    first introduced in Python 3.4. It offers better performance and smaller
    size compared to Protocol 3 available since Python 3.0.

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 :)

@mdkcore0mdkcore0force-pushed thegh-118830 branch 3 times, most recently fromb65e9fb to70676b2CompareJune 12, 2024 17:31
@picnixz
Copy link
Member

Before 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 reacted with thumbs up emoji

@mdkcore0
Copy link
ContributorAuthor

mdkcore0 commentedJun 18, 2024
edited
Loading

Before 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.

no problem, thanks!!

@picnixz
Copy link
Member

picnixz commentedJun 27, 2024
edited
Loading

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).

@encukou
Copy link
Member

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.

picnixz reacted with thumbs up emoji

@hugovk
Copy link
Member

See also thefailed CI check:

Generated files not up to date.
Perhaps you forgot to runmake regen-all orbuild.bat --regen. ;)

@mdkcore0
Copy link
ContributorAuthor

See also thefailed CI check:

Generated files not up to date.
Perhaps you forgot to runmake regen-all orbuild.bat --regen. ;)

oh, cool
I run the mentioned command, should I commit the modified files them (Modules/_pickle.c and Modules/clinic/_pickle.c.h)?

@hugovk
Copy link
Member

Yes please!

mdkcore0 reacted with thumbs up emoji

@encukouencukou merged commitd66b061 intopython:mainJul 19, 2024
@encukou
Copy link
Member

Thank you!

devdanzin and mdkcore0 reacted with hooray emoji

@mdkcore0mdkcore0 deleted the gh-118830 branchJuly 19, 2024 16:44
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@carljmcarljmcarljm left review comments

@hugovkhugovkhugovk left review comments

@picnixzpicnixzpicnixz left review comments

@devdanzindevdanzindevdanzin left review comments

@chris-eiblchris-eiblchris-eibl left review comments

@encukouencukouencukou approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@mdkcore0@carljm@ambv@picnixz@encukou@hugovk@devdanzin@chris-eibl

[8]ページ先頭

©2009-2025 Movatter.jp