gonegown added the comment:
@Amaury:
error message for my bug was:
SyntaxError: None
and for your:
ImportError: No module named b
We've got at least two bugs in one testcase
--
___
Python tracker
<http://bugs.python.org/i
gonegown added the comment:
@Amaury:
Just fine!
It's either another bug in python or 3.1.1 specifics.
--
___
Python tracker
<http://bugs.python.org/i
gonegown added the comment:
@Amaury:
Removing #coding lines or replacing them with #coding: utf-8 makes this test
case working, at least on 4 computers I have been able to test this.
My initial program was consisting of roughly ten files and utf-8 made it work.
@haypo:
"
gonegown added the comment:
@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; unti
gonegown added the comment:
Is there py3k for win32?
And how do I know if #8611 comes from the same source?
Have no idea how they have organized the python core. I'm new to python (about
2 months) and I don't think I will use it for long. It's j
New submission from gonegown :
I have python 3.1.2 fetched from the main site.
imagine two source files:
a.py:
---
# coding: cp1251
import b;
print('A');
---
b.py:
---
print('B');
---
Both reside in the same directory containing at least one non-ascii char
