This is an old revision of the document!
The 24.9.1 Windows installer (x86 and x64) makes a call to the Python interpreter. The Python script called during installation patches the path in a few Python programs in
GMSPython\Scripts. This call can go wrong and there are currently two know reasons for this.
1) The system environment contains the
PYTHONHOME environment variable that points to an incompatible Python version. The installer finishes with a pop-up with “Python has stopped working”:
2) The Windows system is missing some DLLs for the Universal C Runtime. These runtime libraries have been distributed by Microsoft in October 2015 as part of a regular Windows Update KB2999226. You will see a pop-up like this:
Even though the error looks serious it can be safely ignored. GAMS will work properly. In case the cause of the error is the missing DLLs (2) you will not be able to work with embedded Python code unless you install the missing DLLs (see https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows for details and download instructions). If you try to execute GAMS examples containing embedded Python code without the Universal C Runtime installed you will get an error message like this:
*** Error at line 7: Error executing "embeddedCode" section: The specified module could not be found. (problem occurred when trying to load embpycclib)
The GAMS embedded Python code facility works with the Python 3.6.1 installation that is shipped with the GAMS distribution (unless the command line switch
pySetup is set to 0) independent of the system environment variable
PYTHONHOME and hence no further action is required. Only if you want to run the Python executable in
GMSPython\python.exe you cannot point to a different Python installation via an environment variable
PYTHONHOME and need to unset this variable (
The only effect of the failed Python run during installation is the unchanged Python programs in
pip.exe). If you want to run these, you need to do this from the GMSPython\Scripts directory or run (after fixing the causes for (1) and/or (2)) the program
..\python fixPath.py once in the