|
Size: 1971
Comment: problem with stripped tests
|
Size: 2221
Comment: add information from Python3
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 22: | Line 22: |
| * Python 3.1 is in [[DebianPts:python3.1|testing]] * Python 2.7 is in [[DebianPts:python2.7|experimental]] * Python 2.6 is in [[DebianPts:python2.6|testing]] * Python 2.5 is in [[DebianPts:python2.5|stable and testing]] * Python 2.4 is in [[DebianPts:python2.4|Lenny]] |
|
| Line 37: | Line 43: |
| Line 42: | Line 47: |
| * [[DebianPython/BSP]] |
Contents
Python in Debian
Within the Debian project Python packages are maintained by individual developers and three main teams :
pkg-python maintains the Python compiler/interpreter package.
Debian Python Modules Team maintains Python modules and extensions.
Python Applications Packaging Team maintains some Python applications.
There are also :
debian-python mailing list with all development discussions
#debian-python IRC channel
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
Python 3.1 is in testing
Python 2.7 is in experimental
Python 2.6 is in testing
Python 2.5 is in stable and testing
Python 2.4 is in Lenny
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.