py2exe

Hi,

I'm trying to use sys.setappdefaultencoding() in my application, for which =
I=20
need the application to import sitecustomize.py.

According to the mailing list, I should be able to pass a command line opti=
on=20
'force-imports=3Dsitecustomize' to py2exe, but the force-imports agument=20
doesn't seem to be recognized in the latest version of py2exe.

How can I solve this problem?

Peter

Solved : It was a corrupted file on my system, an __init__.py of ctypes
full of NULL, maybe because of a disk failure or something like that.

Wilk <wilk-ml@...> writes:

> Hi,
>
> I cannot import getpass, is it a bug or i missed something ? :
>
> python2.3.4 on windowsNT4, py2exe 0.5.4

-- 
William - http://flibuste.net

SSB0cmllZCBzb21ldGhpbmdzIGluIHB5MmV4ZToNCg0KIA0KDQpJIHdhbnQgaXQ6DQoNCuKAnE7D
o28gw6kgw6Egw6fDtWVzIMOB4oCdDQoNCiANCg0KVXNpbmcgZW5jb2RpbmcgY3AxMjUyICh3aXRo
IGFuZCB3aXRob3V0IOKAnC0tcGFja2FnZXMgZW5jb2Rpbmdz4oCdKToNCg0KSSBoYXZlIGl0Og0K
DQrigJxOw5JvIMOaIM6yIMOewqdlcyDilLTigJ0gLSBpdHMgYWxsIHdyb25nIGhlcmXigKYNCg0K
IA0KDQpVc2luZyBlbmNvZGluZyBjcDg2MCAod2l0aCBhbmQgd2l0aG91dCDigJwtLXBhY2thZ2Vz
IGVuY29kaW5nc+KAnSk6DQoNCkkgaGF2ZSBpdDoNCg0K4oCcTsOkbyDDqSDDoSDDp8O2ZXMgw6Xi
gJ0gLSAoYmV0dGVyLCBidXQgc3RpbGwgc2hvdyDigJzDo+KAnSBhcyDigJzDpOKAnSBhbmQg4oCc
w7XigJ0gYXMg4oCcw7bigJ0sIGFuZCBhbiDigJzDgeKAnSBhcHBlYXIgYXMgYW4g4oCcw6XigJ0p
DQoNCiANCg0KV2hpY2ggZW5jb2RpbmcgSSBtdXN0IHVzZT8gVGhlcmUgaXMgb3RoZXIgZm9yIHBv
cnR1Z3Vlc2U/DQoNCiANCg0KUFMuOiBjcDEyNTIgd29ya3MgcmlnaHQgaW4gcHl0aG9uIHNoZWxs
LCBidXQgd2hlbiBjb21waWxlZCB3aXRoIHB5MmV4ZeKApg0KDQogDQoNCg==

Hi, i use Python 2.3.4, and py2exe 0.5.4. I did a setup.py:

---------------------------------------------------------

#setup.py

=20

from distutils.core import setup

import py2exe

=20

setup(console =3D [{"script": "GerAstro.py", "icon_resources": [(1,
"GerAstro.ico")]}])

options =3D { 'py2exe': { 'packages': 'encodings' } }

---------------------------------------------------------

=20

It works, but I use cp1252 encoding in my script. It works fine in =
Python
shell, but after compiled its all wrong=85

=20

I receive wrong graphical accentuation (I use =E3, =E9, =E7 etc=85 =
brazillian
portuguese)

=20

Other problem, when compiling I receive this message:

UnicodeDecodeError: =91ascii=92 codec can=92t decode byte 0xe1 in =
position 54:
ordinal not in range(128)

=20

What=92s that?

Hi,

I was trying to run a py2exed program from the root directory of a CD 
on Windows. I was getting ImportErrors and that was probably because 
the sys.path was: ['D:\\\\library.zip'] Unless I'm unescaping that 
wrong (D:\\library.zip), it looks like there's an extra backslash.

I simply moved the program to a subdirectory on the CD and it now works 
fine, even when autorun.

Just mentioning this for the record.

hi ,

how can i exactly save some python script  in exe format

i use python script1.py py2exe

but it just runs - no exe anywhere !!

Thanks

When I run setup.py py2exe, everything proceeds swimmingly until the
last line, when I get this message:
----
The following modules appear to be missing
['Numeric']
----

I think this is related to a wxWindows module which first tries to
import numarray and then, if that fails, resorts to using Numeric (its
old name.) As the build script does successfully locate numarray, this
shouldn't be a problem.

But when I go to fire up one of the .exe's I just generated, I get this:
----
Fatal Python error: Call to API function without first calling
import_libnumarray() in Src\_convmodule.c

This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more
information.
----

I'm stumped. Anyone have know what's going on here? Thanks,

-- 

Jonathan

Hello everybody,

I'm having a problem loading py2exe on to win 95 me.
python 2.3.4 is loaded and running. I have also installed unicows into 
the DLL directory.   But, every time I try to run 
py2exe-0.5.4.win32-py2.3.exe I get a Windows error message.

"This program has performed an illegal operation and will be 
shutdown."

Additional details reported are:

PY2EXE-0 caused a invalid page fault in module COMCTL32. DLL at 
0137:bff01a53 and then lists a series of registers.

I would appreciate any help.

Jim

Hi,
 I'm wondering if it's somehow possible to run py2exe on a Linux machine and
generate windows binary? I'd like to autogenerate the windows versions from
Makefile while developing, maybe using wine is an option? Someone tried it? 

thx,
-- 
Kender
Q: In Python, how do you create a string of random characters?
A: Read a Perl source file
 [CherryPy Tutorial]

aurora <aurora00@...> writes:

> Hi all! Since py2exe embeds Python runtime. Do you need to include or
> display any license document in the distribution?

Question like these can only be answered by laywers.  Or read the
license(s) yourself, and interpret it.

Thomas

I build this project on win 2000.
Runs out of c:\polldir.

The gui program, settings.exe, uses tkinter and Pmw
The comm program, remote.exe, uses pyserial.
both work great.
I copy the project to a win2000 machine with no python,
works great.
I copy the project to a WinXP home edition machine,
works great.
I copy the project to a WinXP Pro with service pack2,
NOTHING works. Aarrgh!!  Logs follow.

settings.exe complains about not being able to find tcl8.4
in \lib but its right there in \polldir.  ???

remote.exe can't load some dll but it doesn't say what. ???
Any ideas?  Thanks.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\poltest>cd \polldir

C:\polldir>settings

C:\polldir>dir *.log
  Volume in drive C is IBM_PRELOAD
  Volume Serial Number is 147E-F07E

  Directory of C:\polldir

11/18/2004  09:59 AM               796 SETTINGS.EXE.log
                1 File(s)            796 bytes
                0 Dir(s)  30,047,117,312 bytes free

C:\polldir>type settings.exe.log
Traceback (most recent call last):
   File "settings.py", line 211, in ?
   File "settings.py", line 31, in __init__
   File "settings.py", line 34, in mkmainwin
   File "Tkinter.pyc", line 1564, in __init__
_tkinter.TclError: Can't find a usable init.tcl in the following 
directories:
     C:/lib/tcl8.4 C:/lib/tcl8.4 C:/library

This probably means that Tcl wasn't installed properly.



C:\polldir>

C:\polldir>remote
Traceback (most recent call last):
   File "remote.py", line 3, in ?
   File "serial\__init__.pyc", line 13, in ?
   File "serial\serialwin32.pyc", line 9, in ?
   File "win32file.pyc", line 9, in ?
   File "win32file.pyc", line 7, in __load
ImportError: DLL load failed: The specified module could not be found.

David Bolen <db3l@...> writes:

> I was wondering if the python DLL patch process (not quite sure at
> this point why py2exe patches the DLL, but I assume its useful for
> some situations) could try to verify that it's patching properly?

Unfortunately not, as it seems.  It uses the official win32 functions,
and they don't detect an error.

> I like to use UPX'd executables in some situations, particularly with
> packaged up Python apps, since the files aren't going to be shared
> with anyone else anyway, so the lack of OS-sharing due to the
> compression doesn't bother me.
>
> Anyway, I know py2exe doesn't currently support UPXing its output
> directly, but I found I could just upx the files in the dist tree and
> they weren't updated unless they changed (in general uncommon for the
> system libraries).  That is, except for python23.dll.  Py2exe wants to
> keep patching it every time, and unfortunately it doesn't seem to
> check that it's safe to do so, so the patch process corrupts the upx
> file.

There was also a bug report about this on SF's tracker.  I have now (in
CVS) changed to code so that the patching is only done when a fresh
python.dll has been copied to the dist directory.  That should fix this
problem.

Oh, and the patching was done for this reason: Python uses the string
resource in python.dll to locate additional paths in the registry.  So,
the frozen servers could still have these entries from the registry
inserted in sys.path and load modules from the file system in cases
where the Python distribution is installed on the target system.
Patching avoids this.

Thomas

Alexander Eisenhuth <newsuser@...> writes:

> Hello,
>
> first I want to thank a lot to all who worked on the COM integration
> of py2exe.
>
> As I've seen in this list there seems to be a problem with a windows
> target and logging in a wider sense, so maybe this issue depends also
> on that (I really don't know).
>
> After I build my COM-server as EXE with :
>
> myServer = Target(
>     description = ""
>     create_exe = True,
>     create_dll = False
>     other_resources = [<manifest stuff from advanced example of pyToExe>]
>     dest_base = "myServer"
> )
>
> I can't get traces of it (stdout). I register myServer.exe with
> --register --debug.
>
> Maybe this is a restriction to COM-servers ??? Or there is a magic-flag ???

I have no time to investigate this myself, but here is a hint.
EXE COM servers are build (iirc) with the py2exe equivalent of
pythonw.exe, and the file py2exe\boot_common.py contains code which
redirects everything written to sys.stdout or sys.stderr into a file.
I would guess traceutil (or how is it called?) does also work by
redirecting stdout/stderr - you could try to comment out the code in
boot_common.py, rebuild, and look if it works now.  If so, a patch would
be nice.

Thomas

aurora <aurora00@...> writes:

> I've just gone through the advance example and created a win32 service.
> I've done C++ service and it was never as easy as py2exe. py2exe rocks!
>
> I do encountered one problem below:
>
> running py2exe
> *** generate typelib stubs ***
> Traceback (most recent call last):
>     File "D:\Program
> Files\Python23\Lib\site-packages\py2exe\samples\advanced\setup.py", line
> 134, in ?
>       windows = [test_wx],
>     File "D:\PROGRA~1\Python23\lib\distutils\core.py", line 149, in setup
>       dist.run_commands()
>     File "D:\PROGRA~1\Python23\lib\distutils\dist.py", line 907, in
> run_commands
>       self.run_command(cmd)
>     File "D:\PROGRA~1\Python23\lib\distutils\dist.py", line 927, in
> run_command
>       cmd_obj.run()
>     File "D:\PROGRA~1\Python23\Lib\site-packages\py2exe\build_exe.py", line
> 183, in run
>       self._run()
>     File "D:\PROGRA~1\Python23\Lib\site-packages\py2exe\build_exe.py", line
> 214, in _run
>       self.typelibs)
>     File "D:\PROGRA~1\Python23\Lib\site-packages\py2exe\build_exe.py", line
> 1252, in collect_win32com_genpy
>       makepy.GenerateFromTypeLibSpec(info, bForDemand = False)
>     File "D:\PROGRA~1\Python23\lib\site-packages\win32com\client\makepy.py",
> line 194, in GenerateFromTypeLibSpec
>       tlb = pythoncom.LoadRegTypeLib(typelibCLSID, major, minor, lcid)
> pywintypes.com_error: (-2147319779, 'Library not registered.', None, None)
>
>
> After some research it seems that the example make use of a WMI module.
> I'm not sure what it is but it seems that it is not essential for making a
> service. So I take the liberty and removed a few WMI related stuff from
> setup.py to get it work. Just what to make sure what I did is OK. And I
> wonder if it make sense to break down the advance example to one related
> to WMI and another one that does not so that it has less dependency.

The advanced sample shows advanced techinques, so I dont't think I want
to fix it.  After all, you figured it out!
If you want to suggest some explanation to insert into the adnvanced
setup script, I'll accept a patch ;-).

Thomas