From: Denis B. <bar...@bp...> - 2004-06-17 08:26:30
|
Hello, as far I know, Python source are easy recoverable from bytecode (*.pyc) files, so you can send *.py ;-) I suppose, for more detailed diagnostic you can use python profiler (profile module) or logging module (for timestamping function calling). Regards, Denis Barmenkov Date: Wed, 16 Jun 2004 08:25:45 +0200 From: "POYEN OP Olivier (DCL)" <Oli...@cl...> To: <py2...@li...> Subject: [Py2exe-users] Startupt time: .exe slower than .py Hi all, just subscribe to py2exe ml. python 2.3 py2exe 0.5.0 wxpython 2.4.2.4 Pentium 4, 512 Mb RAM/3.2 Ghz - Win 2K SP3 This may be a known issue (/feature) or perhaps this is totally = understandable once you know py2exe internals, but I have different = startup time between script and its .exe I saw that between a script launched in command line=20 python myscript.py and an executable from the same file made with py2exe ./myscript.exe the .exe is noticably slower to launch than the script The script is a wxpython software and after initialisation and creation = of the gui, I start the initialization of a cache system, which output = debug stuff. The whole system is also connecting to another propriatery system to = fecth data.=20 But anyway, those connections should "spend" the same time wheter they = came from script or from .exe And clearly, my debug output are far more slower to be printed in the = .exe stuff than in the script version. To give you borring details, both files, (sources, executables, = images,..) are on the networks, not on the local HD.=20 I really don't know why, but, like always, the only things I can deliver = are .exe and not .py files.=20 So, I have to stay with .exe. I tweak my script a lot, and it's startup time is reasonably low, but = the startup time of the .exe is like 4 or 5 times longer.=20 Is this a known issue, or the consequence of the whole py2exe system, = and then I can't do anything about it ?=20 Or does it came from the fact that I have to read from a big librairie = .zip file (2 MO. not so huge), in order to load primary modules, which = turns to be slow. Is there anything I can do about it ?=20 Or is there any debug options I can turn on to know more about what = happens ? Thanks for any comments/help/stuff..... And by the way, did I really need to say that I enjoy using py2exe, that = without it I would be obliged to use VB or VisualC++, or worse to stop = using python.=20 Thanks for giving my job some hapy(thon)ness ! ---OPQ Long signature following --__--__-- _______________________________________________ Py2exe-users mailing list Py2...@li... https://lists.sourceforge.net/lists/listinfo/py2exe-users End of Py2exe-users Digest |