Differences between revisions 19 and 20
Revision 19 as of 2010-01-03 10:51:47
Size: 1699
Editor: HenriLeFoll
Comment: move bytecode to Python , add mailing list & IRC
Revision 20 as of 2010-02-26 11:06:43
Size: 1971
Editor: ?techtonik
Comment: problem with stripped tests
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
On the [[http://lists.debian.org/debian-python/recent|debian-python mailing list]] you can follow the latest developments.

On
[[IRC]] some people use the channel #debian-python to discuss

For more information read the
[[DebianPythonFAQ|FAQ]] and this [[DebianPython/ListOfPackages|incomplete list of Python's packages in Debian]]
There are also :
 * [[http:
//lists.debian.org/debian-python/recent|debian-python mailing list]] with all development discussions
 * [[irc://irc.o
ftc.net/debian-python|#debian-python]] [[IRC]] channel
 * [[DebianPythonFAQ|FAQ]] and [[DebianPython/ListOfPackages|incomplete list of Python's packages in Debian]]
Line 34: Line 32:
== 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.

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.

?Python 2.6 as default is a goal for squeeze

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@l.d.o mailing list and contribute to ?DebianPython/Tutorial.

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

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