[issue23611] Pickle nested names with protocols < 4

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

[issue23611] Pickle nested names with protocols < 4

Roundup Robot added the comment: New changeset f78b9f700d45 by Serhiy Storchaka in branch 'default': Issue #23611: Fixed enums pickling tests. Now all picklings work with all https://hg.python.org/cpython/rev/f78b9f700d45 -- ___ Python tracker

[issue23611] Pickle nested names with protocols < 4

Roundup Robot added the comment: New changeset ca12465418bd by Serhiy Storchaka in branch 'default': Issue #23611: Serializing more "lookupable" objects (such as unbound methods https://hg.python.org/cpython/rev/ca12465418bd -- nosy: +python-dev ___ P

[issue23611] Pickle nested names with protocols < 4

Serhiy Storchaka added the comment: Issue23403. But looks it is early yet for this. Note that this patch doesn't modify protocols. It just makes the pickler more smart and able to serialize more objects with existing protocols. It is the same as add pickle support for some type that didn't sup

[issue23611] Pickle nested names with protocols < 4

STINNER Victor added the comment: > It is used in multiprocessing and this is not configurable. Oh, it would be nice to switch to version 4 by default, or make it configurable. I read that the version 4 is faster. -- ___ Python tracker

[issue23611] Pickle nested names with protocols < 4

Serhiy Storchaka added the comment: Pickle is backward compatible and Python 2 usually is able to unpickle data pickled by Python 3 with protocol < 3. The patch doesn't break compatibility. Current default protocol is 3 for compatibility with older Python 3 versions. It is used in multiprocess

[issue23611] Pickle nested names with protocols < 4

STINNER Victor added the comment: Hum, I don't know well the pickle module. Is it backward compatible? Should Python 2 be able to unserialize data serialized by Python 3? If yes, can you patch break this compatibility? It is unclear to me if it makes sense to even modify protocols different th

[issue23611] Pickle nested names with protocols < 4

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23611] Pickle nested names with protocols < 4

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file38390/pickle_nested_names.patch ___ Python tracker ___ ___ Python-bugs-

[issue23611] Pickle nested names with protocols < 4

Antoine Pitrou added the comment: Interesting. I have only skimmed through the patch, but +1 on the principle. -- ___ Python tracker ___ _

[issue23611] Pickle nested names with protocols < 4

Serhiy Storchaka added the comment: Fixed few bugs and added C implementation. -- Added file: http://bugs.python.org/file38393/pickle_nested_names_2.patch ___ Python tracker ___

[issue23611] Pickle nested names with protocols < 4

New submission from Serhiy Storchaka: Proposed patch allows Python implementation of the pickle module to pickle nested names (e.g. methods) with protocols < 4. Pickled data is compatible with old releases. If this is good I'll write C implementation. -- components: Library (Lib) file