Why are ancient SWIG and Inno Setup versions used?

I was wondering why the latest wxPython Classic (3.0.1.1) uses such old versions of SWIG and Inno Setup?

The About dialog of the wxPython demo says that the version of SWIG used is 1.3.29, which is extremely old, considering that the latest version is 3.0.2 (the same as wxWidgets, interestingly).

Also, the wxPython Windows installer uses Inno Setup version 5.4.0, but the latest version is 5.5.5, which includes benefits such as official support for Windows 8. Currently, I have to manually run the installer as administrator (on Windows 8.1, by right-clicking on the EXE in File Explorer and selecting “Run as administrator”), since administrator rights are needed for the installation. If the version of Inno Setup used to create the installer was updated, I think the installer would automatically prompt for the administrator password, which is done by most modern installers and would be much nicer.

– Timothy

IIRC, the version of SWIG used by wxPython is patched and therefore upgrading is not always that easy. Note that wxPython Phoenix is no longer using SWIG, it now uses SIP.

It would probably help Robin if someone could test that Inno Setup 5.5.5 works without problems with the wxPython scripts.

Werner

···

On 10/29/2014 1:38, ps16thypresenceisfullnessofjoy@gmail.com wrote:

I was wondering why the latest wxPython Classic (3.0.1.1) uses such old versions of SWIG and Inno Setup?

The About dialog of the wxPython demo says that the version of SWIG used is 1.3.29, which is extremely old, considering that the latest version is 3.0.2 (the same as wxWidgets, interestingly).

Also, the wxPython Windows installer uses Inno Setup version 5.4.0, but the latest version is 5.5.5, which includes benefits such as official support for Windows 8. Currently, I have to manually run the installer as administrator (on Windows 8.1, by right-clicking on the EXE in File Explorer and selecting "Run as administrator"), since administrator rights are needed for the installation. If the version of Inno Setup used to create the installer was updated, I think the installer would automatically prompt for the administrator password, which is done by most modern installers and would be much nicer.

I looked into this, and it seems pretty complicated to set up things to be able to test it, but I would be pretty surprised if the latest version of Inno Setup didn’t work. I noticed the Inno Setup changelog says that support for Windows NT and lower was dropped in version 5.5, so maybe that’s why wxPython still uses 5.4.

I figured out that the version of Inno Setup has nothing to do with the installer automatically prompting for the Administrator password.

In make_installer.py in the wxPython source, it’s clear that the Inno Setup script for the 64-bit version requires admin privileges, but the 32-bit version doesn’t. On my x64 PC, I still use the x86 version of wxPython, because I am using the x86 version of Python.

Isn’t this a bug? I would expect the installer to always prompt for the admin password, regardless of whether it is for the x86 or x64 version of wxPython, since admin privileges are required to install both.

···

On Tuesday, October 28, 2014 8:38:17 PM UTC-4, ps16thypresence...@gmail.com wrote:

I was wondering why the latest wxPython Classic (3.0.1.1) uses such old versions of SWIG and Inno Setup?

The About dialog of the wxPython demo says that the version of SWIG used is 1.3.29, which is extremely old, considering that the latest version is 3.0.2 (the same as wxWidgets, interestingly).

Also, the wxPython Windows installer uses Inno Setup version 5.4.0, but the latest version is 5.5.5, which includes benefits such as official support for Windows 8. Currently, I have to manually run the installer as administrator (on Windows 8.1, by right-clicking on the EXE in File Explorer and selecting “Run as administrator”), since administrator rights are needed for the installation. If the version of Inno Setup used to create the installer was updated, I think the installer would automatically prompt for the administrator password, which is done by most modern installers and would be much nicer.

– Timothy