[issue23403] Use pickle protocol 4 by default?

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Serhiy Storchaka added the comment: Opened issue34204 for shelve. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue23403] Use pickle protocol 4 by default?

Change by Łukasz Langa : -- pull_requests: +6189 ___ Python tracker ___ ___

[issue23403] Use pickle protocol 4 by default?

Antoine Pitrou added the comment: > Shelve still uses protocol 3 by default. Should it be bumped too? That sounds reasonable. Perhaps open a separate issue for it? -- ___ Python tracker

[issue23403] Use pickle protocol 4 by default?

Serhiy Storchaka added the comment: Shelve still uses protocol 3 by default. Should it be bumped too? -- ___ Python tracker

[issue23403] Use pickle protocol 4 by default?

Antoine Pitrou added the comment: Is there something left to be done here? -- ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Łukasz Langa added the comment: New changeset c51d8c9ba6211d77db639487501f89aa9b4bcbb1 by Łukasz Langa in branch 'master': bpo-23403: Bump pickle.DEFAULT_PROTOCOL to 4 (#6355) https://github.com/python/cpython/commit/c51d8c9ba6211d77db639487501f89aa9b4bcbb1 --

[issue23403] Use pickle protocol 4 by default?

Change by Serhiy Storchaka : -- dependencies: +Repeated Pickler.dump() doesn't reset the state in the C implementation of pickle superseder: parameterize what serialization is used in multiprocessing -> ___ Python

[issue23403] Use pickle protocol 4 by default?

Serhiy Storchaka added the comment: Should we bump the pickle protocol for shelve? -- ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Change by Łukasz Langa : -- keywords: +patch pull_requests: +6064 stage: -> patch review ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Change by Łukasz Langa : -- keywords: +patch, patch pull_requests: +6064, 6065 stage: -> patch review ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Łukasz Langa added the comment: Now that Python 3.3 is dead and 3.4 is soon to follow, it's safe to bump DEFAULT_PROTOCOL to 4. -- assignee: -> lukasz.langa resolution: duplicate -> status: closed -> open ___ Python tracker

[issue23403] Use pickle protocol 4 by default?

Change by Łukasz Langa : -- versions: +Python 3.8 -Python 3.5 ___ Python tracker ___ ___

[issue23403] Use pickle protocol 4 by default?

Change by Serhiy Storchaka : -- nosy: +lukasz.langa ___ Python tracker ___ ___

[issue23403] Use pickle protocol 4 by default?

Changes by Davin Potts : -- superseder: -> parameterize what serialization is used in multiprocessing ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Davin Potts added the comment: Closing in deference to the enhancement described in issue28053. -- nosy: +davin resolution: -> duplicate status: open -> closed ___ Python tracker

[issue23403] Use pickle protocol 4 by default?

STINNER Victor added the comment: Can't we "negociate" the protocol automatically? -- nosy: +haypo ___ Python tracker ___

[issue23403] Use pickle protocol 4 by default?

Antoine Pitrou added the comment: Multiprocessing uses default protocol AFAIK, this is so you can interact with processes using another version of Python. -- nosy: +sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23403

[issue23403] Use pickle protocol 4 by default?

Josh Rosenberg added the comment: multiprocessing spawns the other processes itself from the same executable used to launch the main process. It's not subprocess. How would a different version of Python get involved? -- nosy: +josh.r ___ Python

[issue23403] Use pickle protocol 4 by default?

Serhiy Storchaka added the comment: Multiprocessing uses default protocol and there is no simple (without hacking the stdlib) way to pass the right protocol manually. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23403

[issue23403] Use pickle protocol 4 by default?

Antoine Pitrou added the comment: Because pickles will not be compatible with Python 3.4 anymore. People who want maximum efficiency without compatibility can pass the right protocol manually. -- ___ Python tracker rep...@bugs.python.org

[issue23403] Use pickle protocol 4 by default?

New submission from Serhiy Storchaka: Why not use pickle protocol 4 by default? It allows to pickle some objects which are not pickleable with lower protocols and is more efficient. -- components: Library (Lib) messages: 235498 nosy: alexandre.vassalotti, pitrou, serhiy.storchaka

[issue23403] Use pickle protocol 4 by default?

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23403 ___

[issue23403] Use pickle protocol 4 by default?

Antoine Pitrou added the comment: It is possible to have independent processes communicate together, although that's not the most widely-used feature. See: https://docs.python.org/3/library/multiprocessing.html#multiprocessing-listeners-clients Also: