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 where it actually is in the file system. Open is just calling the OS to do the open, so if no error is raised, the *OS* (Windows) is not raising the error. I don't think there is a bug here, unless it is in Windows itself. ---------- components: +Windows nosy: +r.david.murray, steve.dower, tim.golden, zach.ware _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23039> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
