New submission from John Engelke :
The text:
'If you want to walk an arbitrary filesystem path upwards, it is recommended to
first call Path.resolve() so as to resolve symlinks and eliminate “..”
components.'
should be moved or changed to
'If you want to walk a concrete path upwards
New submission from John Engelke :
The below snippet results in the symlink "/home" resolving as expected.
However, documentation at
https://docs.python.org/3.7/library/pathlib.html#pathlib.Path.resolve suggests,
"If strict is False, the path is resolved as far as possible an
Change by John Engelke :
--
title: Pathlib resolve() on Mac Catalina prepends secret path -> Pathlib
resolve() on Mac prepends path
___
Python tracker
<https://bugs.python.org/issu
Change by John Engelke :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42458>
___
___
Python-bugs-list
John Engelke added the comment:
Thanks @ronaldoussoren. This bug report is flawed for a couple reasons,
notwithstanding some assumptions I made incorrectly. (SIP actually makes
"/home" a symlink so that resolved correctly.) So I am retracting it as-is
because I can't edit th
New submission from John Engelke :
On Mac OS X Catalina+, Pathlib's resolve() method prepends the System Integrity
Protection (SIP) path to the front of the resolved Path, whether you like it or
not.
>>> from pathlib import Path
>>> host_path_str = "/home/som
