Differences between revisions 3 and 5 (spanning 2 versions)
Revision 3 as of 2004-01-12 13:44:17
Size: 295
Editor: cache1-2-ffm-vpn
Comment:
Revision 5 as of 2004-01-12 14:02:11
Size: 619
Editor: cache1-2-ffm-vpn
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

== Solution 1 ==
Line 6: Line 8:
That replaces the [http://starship.python.net/crew/theller/py2exe/ {{{'--force-imports encodings' command line option}}}] from the 0.4 py2exe That replaces the {{{'--force-imports encodings'}}} command line option from the [http://starship.python.net/crew/theller/py2exe/ 0.4py2exe]


== Solution 2 ==

Adding {{{'encodings', 'encodings.*'}}} to includes includes ALL encodings. I'm perfectly happy with only having latin-1 present (at least for some application, which will only be used in western europe)

so recommended adding {{{'encodings', 'encodings.*'}}}

20041201HAM

Encoding

== Solution 1 ==

In py2exe 0.5, if the encodings are not found in the built exe, add these two to the includes: 'encodings', 'encodings.*'

That replaces the '--force-imports encodings' command line option from the [http://starship.python.net/crew/theller/py2exe/ 0.4py2exe]

== Solution 2 ==

Adding 'encodings', 'encodings.*' to includes includes ALL encodings. I'm perfectly happy with only having latin-1 present (at least for some application, which will only be used in western europe)

so recommended adding 'encodings', 'encodings.*'

20041201HAM

EncodingsAgain (last edited 2008-07-08 11:27:44 by localhost)