From: <Mar...@am...> - 2006-11-03 15:25:55
|
Hi There, We use Python 2.3.3 (still) and were on py2exe 0.5.4. We recently built an application that required unicode, and 0.5.4 executables failed because they did not package up the encodings package properly. So, we decided it was time to upgrade. ;o) After some fairly careful testing to ensure 0.6.5 would work, we made the upgrade to our build machine. Unfortunately we noticed a massive bug in our built product that is a showstopper. If you execute our built executables from the directory in which they reside, there is no problem. Everything works fine. However, we have a command prompt that sets up the PATH in Windows to our bin folder where the executables reside so you can execute the .exes from anywhere. If you try this with the new 0.6.5-created executables, you get the following error on all of our executables: Traceback (most recent call last): File "C:\Python23\lib\site-packages\py2exe\boot_common.py", line 92, in ? zipimport.ZipImportError: can't decompress data; zlib not available Traceback (most recent call last): File "nvmd.py", line 17, in ? zipimport.ZipImportError: can't decompress data; zlib not available I have no idea why it can't find zlib, because there is a zlib.pyd in the same folder as the executable. Any ideas, before we roll everything back to 0.5.4 and rebuild our product? I have a release today, so I'm a bit stressed about this... Thanks in advance, Mark. AMI Semiconductor - "Silicon Solutions for the Real World" NOTICE: This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received. |