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 steve.dower
Recipients CarK, SilentGhost, eryksun, paul.moore, steve.dower, steven.daprano, tim.golden, zach.ware
Date 2019-07-09.10:11:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562667068.99.0.786768619633.issue37517@roundup.psfhosted.org>
In-reply-to
Content
Presumably this is linked to issue37515 (why not just repurpose that one?), but I'm inclined to think this is okay provided:

* if the operation succeeds, no error/message is displayed
* if the operation fails, we only update the error message if one of the special filenames is the target

So probably this ought to be a special case in PyErr_SetFromWindowsErrWithFilename(). And either we need to search the string for the special names or find an API that will clarify it (GetFileAttributes?).

I definitely do not want every error message suggesting that this edge case may be the cause, and I don't want to prevent people using these names or purpose for their actual uses.
History
Date User Action Args
2019-07-09 10:11:09steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, steven.daprano, SilentGhost, zach.ware, eryksun, CarK
2019-07-09 10:11:08steve.dowersetmessageid: <1562667068.99.0.786768619633.issue37517@roundup.psfhosted.org>
2019-07-09 10:11:08steve.dowerlinkissue37517 messages
2019-07-09 10:11:08steve.dowercreate