On Mon, Jan 24, 2011 at 7:36 AM, Giovanni Bajo <[email protected]> wrote:
> Well, it's going to need some patching for sure. It's not supported at
> the moment. I'm not even sure it's the correct way forward for 2.x at
> least: Python has many bugs on Windows when it comes to handling unicode
> filepaths which are not MBCS-encodable (using the system encoding).
>
> Eg: if you are on a Western Windows and you try to run a .py file within
> a directory with japanese characters, you get an error and the program
> does not start.
I'm finding this out the hard way, I guess. The above is why I'm
starting to think that unicoding the bootloader was a useless thing to
do. Perhaps the changes that I worked on there will be useful for a
Py3k branch, but I'm beginning to think that there is no benefit at
all in Python 2.x. Does that jive with your thinking?
> As you probably know, Windows has two underlying APIs: the full Unicode
> (W suffix in API calls) and the MBCS-encoded-with-system-encoding (A in
> API calls). There are non-trivial point in Python itself and the Python
> libraries where only the A version ("str" data type) is supported.
>
> So my suggestion is not to force unicode paths in sys.path, but only
> resort to them when there is no other way to represent them (= when mbcs
> encoding fails). At that point, if zipimporter does not support unicode
> path, it means that .egg files will not work, and it will stay as a
> missing feature because of a Python bug.
>
>> I'm not sure at all why the call to
>> zipimport.zipimporter triggers an encoding either.
>
> Probably a bug.
Since I couldn't find any "zipimporter*" files in the Python
distribution, I suppose that zipimporter is built into the Python
library itself, and it doesn't have unicode support, which scuttles
what I was trying to do. If it matters, I'm using Python 2.6.5.
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
