View Issue Details

IDProjectCategoryView StatusLast Update
0000579ascendpygtk guipublic2013-10-25 13:09
Assigned To 
Status newResolutionopen 
PlatformWindowsOSWindowsOS Version7
Product Version0.9.8 
Target VersionFixed in Version 
Summary0000579: Installation and runtime are not compatible with the use of the PyGTK all-in-one package.
DescriptionThe configuration of the GTKLIB variable in ascend does not support the use of the all-in-one PyGTK installer. The all-in-one installer includes GTK, PyGTK, PyCario and PyGObject and manages the configuration of the python path to ensure that everything is configured correctly. From a very brief review, it appears to me that the ascend launch script looks to configure the GTK library paths on its own and this causes a problem.

This behavior is only observed after the installer is 'tricked' into working by installing GTK manually and adding it to the system path. Of course, this indicates that the installer is also incompatible with the use of the all-in-one PyGTK installer.
Steps To ReproduceInstall GTK, add it to the path.
Install PyGTK all-in-one installer.
Install Ascend
Run Ascend
Additional InformationThis seems like a barrier to accessibility on Windows platforms. The GTK community encourages the use of the all-in-one installer to minimize barriers to use of PyGTK applications.
TagsNo tags attached.




2013-10-25 08:46

administrator   ~0000988

Hi Jordan

What happens in the installer in this case, does it detect GTK but not PyGTK, or does it detect neither?

What is the correct way of detecting all fully functioning PyGTK when the 'all-in-one' installer is running. Preferably by looking at the Windows registry rather than having to run Python -- is there a way?



2013-10-25 13:01

reporter   ~0000989

Hi John. Without the standalone GTK+ installed, the installer would fail to install the GUI, I don't recall if there was a distinction between PyGTK and GTK being installed.

I'm not certain if there is a way to detect the installation of PyGTK. I expect that there must be a registry entry though.

The operation of the launch script is a separate problem though. The all-in-one PyGTK installer manages the path when Python launches. If all is working, "import gtk" should succeed.


2013-10-25 13:09

administrator   ~0000990

Last edited: 2013-11-07 21:35

View 2 revisions

Hi Jordan

The detection of different bits and pieces is implemented in NSIS code as shown here:


Issue History

Date Modified Username Field Change
2013-10-25 00:53 jordan New Issue
2013-10-25 08:46 john Note Added: 0000988
2013-10-25 13:01 jordan Note Added: 0000989
2013-10-25 13:09 john Note Added: 0000990
2013-11-07 21:35 john Note Edited: 0000990 View Revisions