lgkeron.blogg.se - Py2exe python 3.5 download sourceforge

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE HOW TO#
#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE .EXE#
#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE INSTALL#
#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE PATCH#
#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE CODE#

If we ever manage to fix this, then we can try to reduce this further down to the 1 and 0 options. About bundle_files=0, for the moment, I would address one issue at the time, which is bundle_files=2, because we would need this for any lower bundle value. Now, I see that your last edit seems to agree with this statement. In addition, judging on these findings and my investigation from the comment above, I think the problem is solely in the source part of the package, most likely in MemoryModule.c, and has nothing to do with the DllFinder or with pescan.

I would also encourage other users that need this option to use Python 3.7 or lower, hence the new issue title. Docker) or to double check your environment. Therefore, I would encourage you to try again in an isolated environment (e.g. So, to clarify, I can run the test executable packed with bundle_files=2 with the existing, untouched codebase on Python <=3.7.

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE CODE#

In all the tests, all the code was not changed, including the pefile related parts. I also just ran the same test in the CI flow on this repository, running on the latest development branch, and obtained exactly the same result: The test was a PASS on Python 3.6 and 3.7, and a fail on Python 3.8 and 3.9. I performed the test described in this issue with latest py2exe (0.10.1.0) and bundle_files=2. Mmmh, then indeed we do have a misunderstanding.

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE PATCH#

So on 3.8 it doesn't work at all on 3.7, latest works unless you need bundle_files=0, then you need to patch out / rewrite that one commit. Example with bundle_files=2 or 1 runs fine. I think these may be 2 interconnected issues, on 3.8 it just plain doesn't work, but on 3.7 it broke.Įdit: I reran the whole thing again, and it seems that on python 3.7, only bundle_files=0 needs the fix that I described. The breaking commit was b25a41e, adding pewalker (of which pescan is a later rewrite). I am not sure myself why it would matter but i went up the commit history (skipping license/readme amendments and tests/appveyor fixes), on python 3.7, from py2exe 0.9.3.2, the last known good one.

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE INSTALL#

Only if i remove the pescan code from dllfinder, rebuild the wheel & install it to a fresh python 3.7 environment does it run without issues. 3.7, and install py2exe=0.10.1.0 (current) with pip install py2exe, the crash is reproducible with the example in all cases. The moment we need to import a PYD file from the zip, hence, to rely on _memimporter, the crash happens.Īfter compiling the py2exe stubs with debug enabled, and after passing the py2exe and Python PDB debug symbols to WinDbg, I got the following trace of the crash: Which confirmed my suspicions: the executable runs fine as long as it has to rely on zipimport. # found _ctypes.pyd in zipfile C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip # trying C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\_ctypes.pyĮrror loading _ctypes: can't find module '_ctypes' # trying C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\_ctypes.pyc # trying C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\_ctypes\_init_.py

# trying C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\_ctypes\_init_.pyc # trying C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\ctypes\_init_.pyc If you need more information about py2exe, visit the official site.Import zipextimporter # loaded from Zip C:\Users\Alberto\Documents\py2exe\tests\functional\bundlefiles_test\dist2\library.zip\zipextimporter.pyc

py2exe hasn't been updated since 2008, so it is not going to work with Python 3.

In that case you will get a runtime error when you try to access a functionality that uses the external library.

If you have imported third party libraries, make sure to test all of the applications functionality before you ship the software, because sometimes the executable is created, but some libraries are missing.

However it is not backwards-compatible: if you create the executable in Windows 7 it is not going to run on Windows XP.

The executable created most of the time is forward compatible: If you create the executable in Windows XP, it will run in Vista and 7.

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE .EXE#

exe file.įinally please take into account the following recommendations: Then just copy the dist folder to the other computer and execute the.

#PY2EXE PYTHON 3.5 DOWNLOAD SOURCEFORGE HOW TO#

A good guide explaining how to do this can be found here. The final step to be able to run the executable on other computers, is that the computer running the executable needs to have the Microsoft Visual C++ 2008 Redistributable package installed.