[issue17213] ctypes loads wrong version of C runtime, leading to error message box from system
Tom Edwards added the comment: Still an issue in 3.3.3. Igor's fix still works, thankfully. -- nosy: +Artfunkel versions: +Python 3.3 -Python 2.7 ___ Python tracker <http://bugs.python.org/issue17213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17213] ctypes loads wrong version of C runtime, leading to error message box from system
Changes by Tom Edwards : -- versions: +Python 2.7 ___ Python tracker <http://bugs.python.org/issue17213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23463] Incorrect behaviour when opening files containing colons on Windows
New submission from Tom Edwards:
Consider this script:
f = open("bug>test.txt",'w')
f.write("hello")
f.close()
On Windows the first line will throw an OSError exception because the character
'>' is not valid in an NTFS filename. This is correct.
Now consider this script:
f = open("bug:test.txt",'w')
f.write("hello")
f.close()
This script will complete without error, and f.write will return 5. This
despite the colon character also being invalid in NTFS filenames!
The output of the second script is an empty file called "bug" in the working
directory. I expect it to throw the same exception as the first script.
--
components: IO
messages: 235964
nosy: Artfunkel
priority: normal
severity: normal
status: open
title: Incorrect behaviour when opening files containing colons on Windows
type: behavior
versions: Python 3.4
___
Python tracker
<http://bugs.python.org/issue23463>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23463] Incorrect behaviour when opening files containing colons on Windows
Tom Edwards added the comment: Ha! What a feature. Thanks for the link. Maybe I'm rehashing old arguments, but I still think that Python's behaviour in this case is wrong. This is very surprising behaviour to anyone who isn't intimately familiar with NTFS and should not be something that in invoked silently. Currently *everyone* who wants to open a file is expected to perform their own test for colons in the path, particularly those who are generating filenames from user data. (Unless they actually want to write to an alternate stream of course, but how often does that happen?) This is behaviour also introduces a cross-platform inconsistency, as a filename on NTFS means something slightly different from a filename on any other file system. Would it be wise for open() to only accept NTFS alternate stream path syntax if a special character is present in the 'mode' argument? -- components: -Windows resolution: not a bug -> status: closed -> open ___ Python tracker <http://bugs.python.org/issue23463> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
