[New-bugs-announce] [issue8988] import + coding = failure (3.1.2/win32)

gonegown report at bugs.python.org
Sun Jun 13 12:50:35 CEST 2010

New submission from gonegown <nomedocac at gmail.com>:

I have python 3.1.2 fetched from the main site.

imagine two source files:

# coding: cp1251
import 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 <report at bugs.python.org>

More information about the New-bugs-announce mailing list