[issue23463] Incorrect behaviour when opening files containing colons on Windows

R. David Murray added the comment: Python just exposes the OS filename semantics, it doesn't judge them :) This is just as true on linux as it is on Windows. -- nosy: +r.david.murray resolution: -> not a bug status: open -> closed ___ Python tracker

[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 in

[issue23463] Incorrect behaviour when opening files containing colons on Windows

Tim Golden added the comment: Colons are valid in filenames to introduce Alternate Data Stream: https://msdn.microsoft.com/en-us/library/cc422524.aspx -- ___ Python tracker ___

[issue23463] Incorrect behaviour when opening files containing colons on Windows

Changes by Tim Golden : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs

[issue23463] Incorrect behaviour when opening files containing colons on Windows

Changes by SilentGhost : -- components: +Windows nosy: +steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___ Python-bugs-list

[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.t