Python

Python executable and runtime

• Python commandline interpreter, and libraries.
• The interpreter can be invoked as python in the osgeo4w shell.
• The Python interpreter is not associated with the .py extension in the shell, so you can run .py files directly.
• Documentation is not included (beyond builtin doc strings)
• Tcl support is not included.
• NumPy is a distinct add on package due to it's size.

category	Commandline_Utilities
requires	msvcrt
version	2.5.2-1

Packager Notes

• This package is harvested from the standard Python 2.5.2 .msi installer from python.org.
• New Python extensions should be unpacked in osgeo4w\apps\Python25\Lib\site-packages
• Include files and libraries are included, but in the apps\Python25 tree. The distutils/sysconfig.py settings should be correct.
• Extensions may need to be compiled with VC7.1 to be compatible.
• etc\ini\python.bat set PYTHONHOME to control sys.prefix and finding of libraries, etc. This should supercede any other python on the system when python is run within the OSGeo4W shell.

Testing: Python 2.7

It's time to upgrade the python distributed with o4w to the current stable upstream release in the 2.x series, namely 2.7 (ticket #219). To that end see RequiresPython for a list of packages which rely on python, and their current status with regard to being py2.7 ready.

Making a Python 2.7 test package

Open tickets

enhancement type tickets:

#114

optional package to register python in Windows registry

#162

pythonwin launcher

Recently closed tickets

defect type tickets:

#844

Python 3.12.4 vulnerable to CVE-2024-3219 & CVE-2024-6923

#823

python3-numba: AttributeError: module 'numpy' has no attribute 'long'

#814

stdlib venv's broken on new Python 3.9.18

#811

Vulnerable Python 3.9.5 executable exists after install latest of QGIS LTR 3.28.14 using the OSGEO4W installer

#782

python3-rasterio 1.3.6-1 binary incompatibility?

#407

Python.exe: import osgeo.gdal_array raise Application Error