[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2019-08-04 Thread Tal Einat
Tal Einat added the comment: Note that the original fix, in PR GH-9133, contained a bug: UUID objects with `is_safe` set to `SafeUUID.unknown` would cause an exception if unpickled with Python <3.7. This was reported by Thomas Wiebe in a comment to a commit in that PR:

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2019-08-04 Thread Tal Einat
Tal Einat added the comment: New changeset a2ea9448c677706d6318eaa71101f08df7604eb9 by Tal Einat in branch '3.7': [3.7] bpo-34621: backwards-compatible pickle UUID with is_safe=unknown (GH-14834) https://github.com/python/cpython/commit/a2ea9448c677706d6318eaa71101f08df7604eb9 --

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2019-07-18 Thread Tal Einat
Change by Tal Einat : -- pull_requests: +14625 pull_request: https://github.com/python/cpython/pull/14834 ___ Python tracker ___

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2018-09-10 Thread Tal Einat
Change by Tal Einat : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2018-09-10 Thread Tal Einat
Tal Einat added the comment: New changeset d53f1cabe8837697df4acb70c9c6537461b5eeda by Tal Einat in branch '3.7': [3.7] bpo-34621: fix uuid.UUID (un)pickling compatbility with older Python versions (<3.7) (GH-9133)

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2018-09-10 Thread Tal Einat
Change by Tal Einat : -- keywords: +patch pull_requests: +8585 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34621] uuid.UUID objects can't be unpickled in older Python versions (<3.7)

2018-09-10 Thread Tal Einat
New submission from Tal Einat : This affects only 3.7, where the new SafeUUID enum was introduced. This was fixed on the master branch (3.8) while implementing issue30977. Fixing this should simply require defining similar __getstate__ and __setstate__ methods as in 3.8. --