[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: > See also #3080 for the full unicode support in the import machinery. I'm confident that I fixed this issue in bpo-3080. I mark this one as a duplicate. -- resolution: -> duplicate stage: test needed -> resolved status: pending -> closed superseder

[issue8988] import + coding = failure (3.1.2/win32)

Irit Katriel added the comment: I think this can be closed as out of date. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue8988] import + coding = failure (3.1.2/win32)

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue8988] import + coding = failure (3.1.2/win32)

Mark Lawrence added the comment: Works for me using 3.4.1 and 3.5.0a0. -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-lis

[issue8988] import + coding = failure (3.1.2/win32)

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: See also #3080 for the full unicode support in the import machinery. -- ___ Python tracker ___ ___ P

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: I tested the example with Python 3.2 (r85691) and the issue looks to be fixed. Can someone else confirm that? I decompressed the ZIP archive, moved into the directory containing a.py and b.py, and called \path\to\python.exe a.py: it works. -- __

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: I tested pybug-import-coding.zip on Windows with my import_unicode branch (see #9425): it works correctly, whereas it fails with py3k (Python 3.2). -- ___ Python tracker _

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: I wrote a patch on import machinery to support unicode characters: see #9425. -- ___ Python tracker ___

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: Then please tell us how to reproduce the "SyntaxError" case -- ___ Python tracker ___ ___ Pyth

[issue8988] import + coding = failure (3.1.2/win32)

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 _

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: > Just fine! > It's either another bug in python or 3.1.1 specifics. What do you mean? what is 'it'? The error I in the session above shows the bug we described first (strange letters in the path makes the program unusable), and shows that the file's en

[issue8988] import + coding = failure (3.1.2/win32)

gonegown added the comment: @Amaury: Just fine! It's either another bug in python or 3.1.1 specifics. -- ___ Python tracker ___ ___ Py

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: Here is what I did, on a machine running Windows XP, with python 3.1.1: - I used 7-zip to extract the attached zip file, in the c:\temp directory. - Then I opened a command prompt, here is an exact copy of the session: C:>cd \temp\█ C:\temp\█>dir Le volu

[issue8988] import + coding = failure (3.1.2/win32)

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: "maybe"... --

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: Did you read my first comment? "This bug is maybe related to #8611" -- ___ Python tracker ___ ___ Py

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: > 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 agree that cyrillic let

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: > File "F:\1home\С\u201e\a.py", line 1, in > And what the hell is this u201e? That should have been a letter! It's probably this symbol: http://www.eki.ee/letter/chardata.cgi?ucode=201e but it has no representation in the console windows you are using; t

[issue8988] import + coding = failure (3.1.2/win32)

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; until the sourc

[issue8988] import + coding = failure (3.1.2/win32)

Amaury Forgeot d'Arc added the comment: > now tell me how the hell can file system encoding be related > to file content encoding?! Why do you say so? I can reproduce your issue, but changing the first line of a.py: # coding: cp1252 to: # coding: utf-8 did not change anything. In the meantim

[issue8988] import + coding = failure (3.1.2/win32)

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 just not serious. --

[issue8988] import + coding = failure (3.1.2/win32)

STINNER Victor added the comment: This bug is maybe related to #8611? Can you try with py3k (python 3.2)? -- ___ Python tracker ___ _

[issue8988] import + coding = failure (3.1.2/win32)

Changes by R. David Murray : -- components: +Interpreter Core -None stage: -> unit test needed type: crash -> behavior ___ Python tracker ___

[issue8988] import + coding = failure (3.1.2/win32)

Changes by R. David Murray : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8988] import + coding = failure (3.1.2/win32)

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 character (try 0xdb) in