This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gonegown
Recipients amaury.forgeotdarc, gonegown, vstinner
Date 2010-06-26.08:24:36
SpamBayes Score 0.00022922088
Marked as misclassified No
Message-id <1277540679.52.0.0401537977923.issue8988@psf.upfronthosting.co.za>
In-reply-to
Content
@Amaury:
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.

You'll see:
--------
Traceback (most recent call last):
  File "F:\1home\С\u201e\a.py", line 1, in <module>
SyntaxError: None
--------

And what the hell is this u201e? That should have been a letter!
History
Date User Action Args
2010-06-26 08:25:10gonegownsetrecipients: + gonegown, amaury.forgeotdarc, vstinner
2010-06-26 08:24:39gonegownsetmessageid: <1277540679.52.0.0401537977923.issue8988@psf.upfronthosting.co.za>
2010-06-26 08:24:37gonegownlinkissue8988 messages
2010-06-26 08:24:36gonegowncreate