Dear cx-freeze users,
For a long time we've been using py2exe to generate our application
executables for Windows. This generated very slow executables. More
specifically, the import of modules in the executable is very slow, not the
overall performance.
Yesterday we ported cx_freeze 3.0.3 to our toolchain with very pleasant
results: the application got as fast as running the source code using
python. Eg. The application startup took 1min and now takes less than 10seg.
After some study we found out that many of our porting problems in version
3.0.3 were already solved in version 4.0. So we resolved to try it out.
The problem is that version 4.0 generates a slower executable, much like
py2exe does. We really appreciate all the new features of version 4.0,
including the total reorganization of the code, but we are very frustrated
with this speed problem. So I ask:
What is the different between version 3.0.3 and 4.0 regarding the import
of the modules?
What has been added in version 4.0 that could make the import so slow?
Alexandre M. Andrade
Configuration Manager
www.esss.com.br
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
cx-freeze-users mailing list
cx-freeze-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
