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

[STINNER Victor]

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:  -> Full unicode import system

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Irit Katriel]

Irit Katriel  added the comment:

I think this can be closed as out of date.

--
nosy: +iritkatriel
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mark Lawrence]

Change by Mark Lawrence :


--
nosy:  -BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mark Lawrence]

Mark Lawrence added the comment:

Works for me using 3.4.1 and 3.5.0a0.

--
nosy: +BreamoreBoy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8988
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com 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.

--

___
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)

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com added the comment:

See also #3080 for the full unicode support in the import machinery.

--

___
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)

[Éric Araujo]

Changes by Éric Araujo mer...@netwok.org:


--
nosy: +eric.araujo

___
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)

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com added the comment:

I wrote a patch on import machinery to support unicode characters: see #9425.

--

___
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)

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com 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 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]

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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com added the comment:

Then please tell us how to reproduce the SyntaxError case

--

___
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]

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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com 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 encoding doesn't change this.

--

___
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]

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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com 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 volume dans le lecteur C s'appelle Disque dur
 Le numéro de série du volume est D4BA-260C

 Répertoire de C:\temp\█

03/07/2010  11:10REP  .
03/07/2010  11:10REP  ..
08/06/2010  09:1344 a.py
08/06/2010  14:2111 b.py
   2 fichier(s)   55 octets
   2 Rép(s)  58 733 801 472 octets libres

C:\temp\█c:\Python31\python.exe a.py
Traceback (most recent call last):
  File a.py, line 3, in module
import b;
ImportError: No module named b

C:\temp\█notepad a.py
[Replaced encoding with utf-8, then save and quit]

C:\temp\█c:\Python31\python.exe a.py
Traceback (most recent call last):
  File a.py, line 2, in module
import b;
ImportError: No module named b

--

___
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)

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com added the comment:

Did you read my first comment? This bug is maybe related to #8611

--

___
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]

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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com added the comment:

 File F:\1home\С\u201e\a.py, line 1, in module
 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; try import 
sys; print(sys.stderr.encoding) to print the code page used by your console.
In error messages, Python replaces unpritable characters with their escaped 
form: \u where  is the character number.

--

___
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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com 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 letters in the path makes the program unusable. This is 
the bug to fix, and the zip file you attached is a good test case.

But I still don't see how the sources are in utf can influence this. Please 
show me!

--

___
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)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc amaur...@gmail.com 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 meantime, you should refrain from creating directories with characters 
not representable in the terminal window.

@haypo: The problem still exists with py3k at r82150.

--
nosy: +amaury.forgeotdarc

___
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]

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)

[STINNER Victor]

STINNER Victor victor.stin...@haypocalc.com added the comment:

This bug is maybe related to #8611?

Can you try with py3k (python 3.2)?

--

___
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]

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

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

[R. David Murray]

Changes by R. David Murray rdmur...@bitdance.com:


--
nosy: +haypo

___
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)

[R. David Murray]

Changes by R. David Murray rdmur...@bitdance.com:


--
components: +Interpreter Core -None
stage:  - unit test needed
type: crash - behavior

___
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