Differences between revisions 25 and 26
Revision 25 as of 2010-07-13 20:47:08
Size: 2966
Comment: two more links removed
Revision 26 as of 2010-07-14 03:11:44
Size: 2971
Comment: adding "some" to PythonModulesTeam description
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * [[Teams/PythonModulesTeam|Debian Python Modules Team]] maintains Python modules and extensions.  * [[Teams/PythonModulesTeam|Debian Python Modules Team]] maintains some Python modules and extensions.

Python in Debian

Within the Debian project Python packages are maintained by individual developers and three main teams :

There are also :

Supported Python Versions

Debian's latest release Lenny contains multiple Python versions: 2.5 (the default) and 2.4.

Debian Python Policy for Python developers

The Debian Python Policy describes conventions for packaging and distributing Python code in Debian.

The official text is located at http://www.debian.org/doc/packaging-manuals/python-policy/.

Feel free to ask any questions on debian-python@list.debian.org mailing list.

if you want to maintain a Python package, you have to know how the Debian Development works.

Deviations from upstream

Debian distributions modify upstream Python in a few ways that are important to understand. Of course, where at all possible, we try to minimize deviations from upstream, but here is an enumeration of the changes you might encounter on a Debian system (and derivatives, such as Ubuntu).

  • dist-packages instead of site-packages. Third party Python software installed from Debian packages goes into dist-packages, not site-packages. This is to reduce conflict between the system Python, and any from-source Python build you might install manually.

  • The python-setuptools package installs the Distribute fork instead of the standard setuptools.

  • The python-virtualenv also uses distribute by default, but can enable classic setuptools with an optional switch.

Current problems

  • Tests from distributed packages are usually stripped, so it is not possible for user to run them to ensure that package works as expected. This assumes that package maintainers run tests for all possible system configurations. This also makes troubleshooting harder.

See also