Member Avatar for ihatehippies

Anyone know the developers? Anyone else waiting for 3.x support? This is the only thing keeping me from upgrading to python 3.1 ....

  • 4 Contributors
  • 5 Replies
  • 125 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by vegaseat

Dani AI

Generated

A short update for anyone finding this old thread: the packaging situation that stalled Python 3 adoption back in 2009 has changed a lot. The py2exe project was later revived and publishes Python‑3-compatible releases (see the py2exe GitHub), but most people building Windows executables for Python 3 now use PyInstaller or cx_Freeze, and Nuitka is an option if native-code compilation is desired (PyInstaller docs, cx_Freeze docs, Nuitka, py2exe on GitHub).

Practical, repeatable workflow:

  • Use a clean virtualenv and install only the app dependencies so the packager captures what’s needed.
  • Install a packager and build the app. Example with PyInstaller:
pyinstaller --onefile --windowed myscript.py
  • Test the EXE on a clean VM or a fresh Windows install (32 vs 64‑bit, missing MSVC runtimes, and AV differences often show up only on clean systems).

Common pitfalls and fixes: mismatched Python bitness (build 32-bit Python for 32-bit targets), missing MSVC redistributables for C extensions, dynamic imports that require “hidden imports” configuration, and failing to include data files (use spec files or include-data options). If an extension is only available for Python 2, check for a wheel or a maintained fork; otherwise consider replacing that dependency. Packagers’ docs cover debugging modes and how to produce uncompressed builds for tracing problems.

Tying this back: was right that third‑party compiled modules were the main blocker then; today most popular libs provide wheels and packagers handle extensions. For and others holding back upgrades, using PyInstaller or cx_Freeze typically removes the “EXE” barrier; if a strict py2exe requirement remains, verify the current py2exe releases on GitHub/PyPI before deciding.

Recommended Answers

All 5 Replies

Member Avatar for lllllIllIlllI

A lot of developers aren't bothering changing their modules to 3.x I dont upgrade personally because i know if i do i will not be able to use wxPython anymore :(

So yeah, also seeing the last newspost was almost a year ago i have a feeling its not that active anymore... But heh, i could be wrong

Member Avatar for vegaseat

We wouldn't have this problem if Windows machines would ship with Python installed. The real problem is that MS wants to make money with their old VB interpreter.

Member Avatar for ihatehippies

yeah that would be nice. so much for windows 7 being "my idea"

Member Avatar for Gribouillis

We wouldn't have this problem if Windows machines would ship with Python installed. The real problem is that MS wants to make money with their old VB interpreter.

I think that Van Rossum prefers OSX, and he works for Google, which makes 2 other obstacles.

Member Avatar for vegaseat

Python like Java is open source, MS is horrified by this. They had to use Java because of the Internet Explorer. Look what they tried to do to Java a few years ago to make it their own, SUN had to sue them to stop it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.