Differences between revisions 1 and 10 (spanning 9 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.*'

You can do this by adding a line

options = {"py2exe": {"packages": ["encodings"]}},

to your setup.py file.

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 1 as of 2003-11-26 18:11:10 → 
  Size: 150
  Editor: 193
  Comment:
+   ← Revision 10 as of 2004-01-28 00:22:23 → ⇥
  Size: 756
  Editor: p508AAA78
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+== Solution 1 ==
-Line 4:
+Line 6:
-{{{'encodings', 'encodings.*'}}}
+{{{
'encodings', 'encodings.*'
}}}

You can do this by adding a line 
{{{
options = {"py2exe": {"packages": ["encodings"]}},
}}}
to your setup.py file. 

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