RetroSearch Browse

Mon Jun 19 13:27:36 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-June/066210.html

Well, my particular test uses  u'c:/tmp/\u814c'
If that cannot be encoded in mbcs, then mbcs isn't useful.
Note that this is both an issue of python being able to run from an arbitrary install position, and also the ability of users to import and run scripts from any other arbitrary directory.

Kristján

-----Original Message-----
From: Neil Hodgson [mailto:nyamatongwe at gmail.com] 
Sent: 17. júní 2006 04:53
To: Kristján V. Jónsson
Cc: Python Dev
Subject: Re: [Python-Dev] unicode imports

Kristján V. Jónsson:

> Although python has had full unicode support for filenames for a long 
> time on selected platforms (e.g. Windows), there is one glaring 
> deficiency:  It cannot import from paths containing unicode.  I´ve 
> tried creating folders with chinese characters and adding them to path, to no avail.
> The standard install path in chinese distributions can be with a 
> non-ANSI path, and installing an embedded python application there will break it.

   It should be unusual for a Chinese installation to use an install path that can not be represented in MBCS. Try encoding the install directory into MBCS before adding it to sys.path.

   Neil

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/066210.html below:

[Python-Dev] unicode imports