[issue8988] import + coding = failure (3.1.2/win32)
gonegown nomedo...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue8988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8988] import + coding = failure (3.1.2/win32)
gonegown nomedo...@gmail.com added the comment: @Amaury: Just fine! It's either another bug in python or 3.1.1 specifics. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8988] import + coding = failure (3.1.2/win32)
gonegown nomedo...@gmail.com 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: maybe... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8988] import + coding = failure (3.1.2/win32)
gonegown nomedo...@gmail.com 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; 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! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8988] import + coding = failure (3.1.2/win32)
gonegown nomedo...@gmail.com 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 just not serious. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8988] import + coding = failure (3.1.2/win32)
New submission from gonegown nomedo...@gmail.com:
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 character
(try 0xdb) in the _path_.
import will fail with an empty error!
#coding here works fine with utf-8 and fails using any other one
now tell me how the hell can file system encoding be related to file content
encoding?!
I've attached the source
--
components: None
files: pybug-import-coding.zip
messages: 107731
nosy: gonegown
priority: normal
severity: normal
status: open
title: import + coding = failure (3.1.2/win32)
type: crash
versions: Python 3.1
Added file: http://bugs.python.org/file17655/pybug-import-coding.zip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8988
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
