New submission from Philip Lee:
when using open(filename, 'w') on Windows , File names are not allowed to
contain any characters in \/:*?| , however open(filename, 'w') doesn't
throw any exceptions when the file name contains these characters .
I think some warning should be written in the
R. David Murray added the comment:
The argument to open is a path. Some of those characters have a meaning in a
path.
I ran a couple of quick experiments: ab*c.txt fails with an exception.
:16.txt created a file, which I can do an 'ls' and cat (but not rm) on in
git-bash, but I'm not sure
Tim Golden added the comment:
Agree with RDM: we're just passing the path through to the Windows API (on
Windows). We don't generally carry out this kind of pre-emptive check.
--
resolution: - not a bug
stage: - resolved
status: open - closed
___
