This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jh45
Recipients docs@python, jh45
Date 2011-02-17.07:10:34
SpamBayes Score 8.74535e-05
Marked as misclassified No
Message-id <>
A few months ago I read that in 3.2 it will be possible to import modules that are located on paths containing any unicode character. (more precisely, with chars not in the local code page)

After an hour or two trying to get this to work in 3.2rc3, I went looking for clues, and found these 2 messages in which Victor Stinner says this feature is delayed until Python 3.3:

Could you please make it clear in documentation and web pages, that this feature is not working yet. 

The Python 3.2 download page includes this:
"countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables)"
and I guessed this must cover importing from any unicode path, as there was no mention that such importing had been abandoned for this version.

-- jh
Date User Action Args
2011-02-17 07:10:36jh45setrecipients: + jh45, docs@python
2011-02-17 07:10:35jh45setmessageid: <>
2011-02-17 07:10:35jh45linkissue11230 messages
2011-02-17 07:10:34jh45create