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 ronaldoussoren
Recipients Mond Wan, koobs, ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware
Date 2020-07-31.12:06:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596197175.4.0.649140408471.issue41448@roundup.psfhosted.org>
In-reply-to
Content
PureWindowsPath does not know about POSIX paths, it supports the two styles of directory separator that are valid on Windows: '/' and '\'. 

PurePosixPath only supports the single stile of directory separator valid on POSIX systems: '/'. 

On a Posix system backslash is a valid character in a file name and is NOT a directory separator.


The behaviour of Path.resolve() on Windows may or may not be a bug, the documentation is not quite clear. Personally I'd lean toward saying this is a bug, but I defer to a pathlib expert.  Note that path.resolve(strict=True) should raise an error on both platforms when the path does not exists.
History
Date User Action Args
2020-07-31 12:06:15ronaldoussorensetrecipients: + ronaldoussoren, paul.moore, tim.golden, ned.deily, zach.ware, koobs, steve.dower, Mond Wan
2020-07-31 12:06:15ronaldoussorensetmessageid: <1596197175.4.0.649140408471.issue41448@roundup.psfhosted.org>
2020-07-31 12:06:15ronaldoussorenlinkissue41448 messages
2020-07-31 12:06:15ronaldoussorencreate