[issue37517] Improve error messages for Windows reserved file names

Eryk Sun added the comment: > if the operation succeeds, no error/message is displayed Some errors pass silently and may be confusing later on. For example, CreateDirectoryW calls NtCreateFile with the disposition FILE_CREATE and the option FILE_DIRECTORY_FILE (i.e. the call *must* create a

[issue37517] Improve error messages for Windows reserved file names

Steve Dower added the comment: 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 spec

[issue37517] Improve error messages for Windows reserved file names

Eryk Sun added the comment: > Perhaps Windows builds can check for reserved file names and give a > more descriptive error message in the event of IO error? An operation on a reserved DOS device name can also succeed with unexpected results. For example, a script may unintentionally write to

[issue37517] Improve error messages for Windows reserved file names

Change by Steven D'Aprano : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue37517] Improve error messages for Windows reserved file names

New submission from Steven D'Aprano : See #37515. Perhaps Windows builds can check for reserved file names and give a more descriptive error message in the event of IO error? (Eryksun also mentions two reserved names which Microsoft apparently does not document: "CONIN$" and "CONOUT$".) ---