This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author john.engelke
Recipients docs@python, john.engelke
Date 2020-11-25.16:38:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606322337.42.0.83106507565.issue42465@roundup.psfhosted.org>
In-reply-to
Content
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, it is recommended to first call Path.resolve() so as to resolve symlinks and eliminate “..” components.'

Rationale: Wording is confusing as the resolve() method doesn't exist for PurePath, PurePosixPath nor PureWindowsPath. It's unclear that the method applies only to concrete implementations of the Path subclass.

This should be resolved by either altering the above text or (preferably) moving it to the concrete Path section.

NOTE: PurePath (PurePosixPath, PureWindowsPath) operations are described in docs as "purely computational" components that "don’t actually access a filesystem." https://docs.python.org/3.7/library/pathlib.html#pure-paths
History
Date User Action Args
2020-11-25 16:38:57john.engelkesetrecipients: + john.engelke, docs@python
2020-11-25 16:38:57john.engelkesetmessageid: <1606322337.42.0.83106507565.issue42465@roundup.psfhosted.org>
2020-11-25 16:38:57john.engelkelinkissue42465 messages
2020-11-25 16:38:57john.engelkecreate