Differences between revisions 2 and 8 (spanning 6 versions)

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.latin_1'

20041201HAM

-  ⇤ ← Revision 2 as of 2004-01-12 13:43:25 → 
  Size: 255
  Editor: cache1-2-ffm-vpn
  Comment:
+   ← Revision 8 as of 2004-01-12 14:02:55 → ⇥
  Size: 633
  Editor: cache1-2-ffm-vpn
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+== Solution 1 ==
-Line 4:
+Line 6:
-{{{'encodings', 'encodings.*'}}}
+{{{
'encodings', 'encodings.*'
}}}
-Line 6:
+Line 10:
-That replaces the [http://starship.python.net/crew/theller/py2exe/ force Imports] 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.latin_1'
}}}

20041201HAM