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 Kevin.Norris
Recipients Kevin.Norris, eryksun, pitrou, steve.dower, tim.golden, zach.ware
Date 2014-09-05.21:34:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409952899.75.0.860257244039.issue22299@psf.upfronthosting.co.za>
In-reply-to
Content
I'm a little concerned about this fix.  In particular, if I understand the design of the patch correctly, it is intended to produce this behavior:

    Path('C:/foo').resolve() != Path('//?/C:/foo').resolve()

Since both paths are valid and both paths refer to the same file, some developers may find this result counterintuitive.  The Path.resolve() docs do not expressly forbid it, however.

How many developers assume Path.resolve() is always the same for the same file?
History
Date User Action Args
2014-09-05 21:34:59Kevin.Norrissetrecipients: + Kevin.Norris, pitrou, tim.golden, zach.ware, eryksun, steve.dower
2014-09-05 21:34:59Kevin.Norrissetmessageid: <1409952899.75.0.860257244039.issue22299@psf.upfronthosting.co.za>
2014-09-05 21:34:59Kevin.Norrislinkissue22299 messages
2014-09-05 21:34:59Kevin.Norriscreate