Am 11.12.2011 15:26, schrieb Giovanni Bajo:
One issue I had from the start is that PyInstaller only allows for ascii
vs unicode. I think that what it should really allows for is a
user-configurable list of codecs. For instance, many people will want
just utf-8 support, but right now they need to use unicode for that.
I know this is a different topic, but since we're refactoring the codec
support I think it makes sense to know where we're heading. My
suggestion is to add a Codecs() call in spec files to be used like this:
a = Analysys(....)
a += Codecs(["utf-8"])
*Adding* Codeces is quite useless, at least in python 2.6 and 2.7: In
these versions even a simple program includes the encodings, se
buildtest/basic/test_helloworld.py.
*Removing* codecs would make more sence:
a = Analysys(...., excludes=Codecs("*", exclude="utf-8"))
One available codec will be "all" which means "all codecs available in
I would use "*". This symbol is already used in `import` and can never
conflict with any codec name.
the current Python installation". So basically when you use pyinstaller
--unicode, it will generate the line a += Codecs(["all"]) in the spec
file; if you use --ascii, it will not generate a Codecs() line at all.
Okay for --unicod/--ascii to generate code like this (depending on
discussion above).
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult ist Mitglied bei http://www.7-it.de
--
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.
