Python Modules Packaging Team - Policy


Gustavo Franco <>, Raphaël Hertzog <>


GNU GPL v2 or later


Python Modules Packaging Team aims to improve the python modules situation in Debian, by packaging available modules that may be useful and providing a central location for packages maintained by a team, hence improving responsiveness, integration and standardization.

PMPT or just python-modules is hosted at, the Debian GForge installation. We currently have a SVN repository and a mailing list whose email address can be used in the Maintainer field on co-maintained packages.

For more information send a message to:

Joining the team

The team is open to any python-related package maintainer. To be added on the team, please send your request on indicate why you want to join the team: maintain your current packages within the team, help maintain some specific packages, etc. Don’t forget to indicate your Alioth login !

Any Debian developer who wishes to integrate his packages in the team can do so without requesting access (as the repository is writable by all DD). If one wants to be more involved in the team, we still recommend requesting access so that he appears in the public member list displayed on Alioth’s project page.

The team accepts all contributors and is not restricted to Debian developers. Several Debian developers of the team will gladly sponsor packages of non-DD who are part of the team. Sponsorship requests can be sent on the main discussion list or on #debian-python IRC channel (OFTC network).

All team members should of course follow the main discussion list:


A package maintained within the team should have the name of the team either in the Maintainer field or in the Uploaders field.

Maintainer: Debian Python Modules Team <>

This enables the team to have an overview of its packages on the DDPO_website.

  • Team in Maintainers is a strong statement that fully collaborative maintenance is preferred. Anyone can commit to the vcs and upload as needed. A courtesy email to Uploaders can be nice but not required.
  • Team in Uploaders is a weak statement of collaboration. Help in maintaining the package is appreciated, commits to vcs are freely welcomed, but before uploading, please contact the Maintainer for the green light.

Team members who have broad interest should subscribe to the mailing list whereas members who are only interested in some packages should use the Package Tracking System to follow the packages.

Subversion Procedures

We’re using a Subversion repository to maintain all the packages, then if you’re not already using it you will need to install svn-buildpackage.

The repository layout:

Ignore this directory (reserved for future usage).

The source packages are here.

If you or someone wants to play with a package possible breaking the trunk, give it a name and do it here.
For each release, a tag. More information below.
That’s where the main development happens, it should contain only the debian/ subdirectory part of a package.
Documents and stuff that will be or are being published online in our website.


  • To keep your package tree clean as pointed out above, always svn-inject your packages using -o argument.
  • If you svn-inject’ed a package without -o, you should remove upstream sources and run svn propset mergeWithUpstream 1 debian/.
  • Since you are keeping only debian/ directory in the svn tree, you need to put the ‘package-foo’_’version’.orig.tar.gz in tarballs/ a directory above the package, and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.
  • After upload, tag the latest revision running svn-buildpackage --svn-tag-only into ‘package-foo’ directory.
  • You can revert the changelog changes after tagging, running svn revert debian/changelog.
  • If you’re a pbuilder user, you can invoke it using svn-buildpackage --svn-builder pdebuild <args>.

For more information on how to maintain packages within the repository with svn-buildpackage:

Please note that python-modules URLs are different than pkg-perl ones:

Moreover, python-modules still use the default layout: don’t pass -l 2 to svn-inject.

Quality Assurance

The goal of the team is to maintain all packages as best as possible. Thus every member is encouraged to do general QA work on all the packages: fix bugs, test packages, improve them to use the latest python packaging tools, etc.


Copyright (c) 2005-2015 Python Modules Packaging Team. All rights reserved. This document is free software; you may redistribute it and/or modify it under the same terms as GNU GPL v2 or later.