[issue8988] import + coding = failure (3.1.2/win32)
report at bugs.python.org
Sat Jun 26 10:24:39 CEST 2010
gonegown <nomedocac at gmail.com> added the comment:
What you're saying about directory naming is right indeed.
But the case has begun from cyrillic letters in the NTFS path, which I do not use, but the users of my soft do. So putting the program into such directory makes the former unuseable; until the sources are in utf anyway.
I just ran this on another computer and it seemed to work with #coding in a.py. I then added this line to b.py and it failed. I played about 15 minutes inserting the line and removing and changing the directory name.
And I can tell the behaviour for me looks just random!
Though I noticed that addding #coding line to both sources fails more often.
Traceback (most recent call last):
File "F:\1home\С\u201e\a.py", line 1, in <module>
And what the hell is this u201e? That should have been a letter!
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list