Hi again. I have wxPython 2.4.0 and activestate Python 2.2.2 and have
built a wx application that is located on a network share point. This
application was compiled into an executable using py2exe (latest
version). My problem is that whenever a win2k-based machine starts the
application from the share point, it takes about 20 seconds to appear on
screen. While the application is loading, I have noticed that the byte
count of the application slowly climbs to about 7MB then suddenly
increases to 12MB, which is the total size of the application when fully
loaded. However, on NT or XP-based machines, this problem does not
exist. Anyone experienced any similar problems? Thanks guys.
ec wrote:
Hi again. I have wxPython 2.4.0 and activestate Python 2.2.2 and have
built a wx application that is located on a network share point. This
application was compiled into an executable using py2exe (latest
version). My problem is that whenever a win2k-based machine starts the
application from the share point, it takes about 20 seconds to appear on
screen.
Does it take the same time if not located on a network share? Does this machine have different settings from the NT or XP machines for PATH or PYTHONPATH or similar that may include other network drives? Does it behave this way if you run the .py files directly (without py2exe) from the network drive and with Python also installed on the network? (I run this way all the time.)
While the application is loading, I have noticed that the byte
count of the application slowly climbs to about 7MB then suddenly
increases to 12MB, which is the total size of the application when fully
loaded. However, on NT or XP-based machines, this problem does not
exist. Anyone experienced any similar problems? Thanks guys.
Not me.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!