classification
Title: Unpickling Path objects
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Antony.Lee, pitrou
Priority: normal Keywords:

Created on 2016-06-01 09:18 by Antony.Lee, last changed 2016-06-01 09:21 by SilentGhost.

Messages (1)
msg266810 - (view) Author: Antony Lee (Antony.Lee) * Date: 2016-06-01 09:18
Currently, pickling Path objects lead to issues when working across platforms: Paths (and, thus, objects that contain Paths) created on a POSIX platform (PosixPaths) cannot be unpickled on Windows and vice versa.  There are a few possibilities around this issue.

- Don't do anything about it, you should use PurePaths if you care about cross-platform compatibility: this would be pretty awkward, as any call to the Path API would require converting back the PurePath to a Path first.

- Silently convert Paths to PurePaths during pickling (a solution that seems to have been adopted by http://docs.menpo.org/en/stable/api/menpo/io/export_pickle.html for example): it would be better if Paths at least roundtripped correctly within a single platform.

- Convert Paths to PurePaths at unpickling time, only if the platform is different (and possibly with a warning): this is the least bad solution I came up with so far.  Note that calls to the Path API on a "converted" PurePath object would be invalid anyways as the PurePath (being of a different platform) cannot be representing a valid path.

Thoughts?
History
Date User Action Args
2016-06-01 09:21:42SilentGhostsetnosy: + pitrou

type: behavior
versions: - Python 3.5
2016-06-01 09:18:04Antony.Leecreate