2
Python @VER@ for Debian
5
This is Python @VER@ packaged for Debian.
7
This document contains information specific to the Debian packages of
12
[TODO: This document is not yet up-to-date with the packages.]
14
Currently, it features those two main topics:
16
1. Release notes for the Debian packages:
17
2. Notes for developers using the Debian Python packages:
19
Release notes and documentation from the upstream package are installed
20
in /usr/share/doc/@PVER@/.
22
There's a mailing list for discussion of issues related to Python on Debian
23
systems: debian-python@lists.debian.org. The list is not intended for
24
general Python problems, but as a forum for maintainers of Python-related
25
packages and interested third parties.
29
1. Release notes for the Debian packages:
32
Results of the regression test:
33
------------------------------
35
The package does successfully run the regression tests for all included
36
modules. Seven packages are skipped since they are platform-dependent and
37
can't be used with Linux.
40
2. Notes for developers using the Debian python packages:
42
See the draft of the Debian Python policy in /usr/share/doc/python.
44
distutils can be found in the @PVER@-dev package. Development files
45
like the python library or Makefiles can be found in the @PVER@-dev
46
package in /usr/lib/@PVER@/config. Therefore, if you need to install
47
a pure python extension, you only need @PVER@. On the other hand, to
48
install a C extension, you need @PVER@-dev.
50
a) Locally installed Python add-ons
52
/usr/local/lib/@PVER@/site-packages/
53
/usr/local/lib/site-python/ (version-independent modules)
55
b) Python add-ons packaged for Debian
57
/usr/lib/@PVER@/site-packages/
58
/usr/lib/site-python/ (version-independent modules)
60
Note that no package must install files directly into /usr/lib/@PVER@/
61
or /usr/local/lib/@PVER@/. Only the site-packages directory is allowed
62
for third-party extensions.
64
Use of the new `package' scheme is strongly encouraged. The `ni' interface
65
is obsolete in python 1.5.
67
Header files for extensions go into /usr/include/@PVER@/.
70
Installing extensions for local use only:
71
----------------------------------------
73
Consider using distutils ...
75
Most extensions use Python's Makefile.pre.in. Note that Makefile.pre.in
76
by default will install files into /usr/lib/, not into /usr/local/lib/,
77
which is not allowed for local extensions. You'll have to change the
78
Makefile accordingly. Most times, "make prefix=/usr/local install" will
82
Packaging python extensions for Debian:
83
--------------------------------------
85
Maintainers of Python extension packages should read
87
/usr/share/doc/python/python-policy.txt.gz
93
Gregor Hoffleit <flight@debian.org>
95
Last change: 2001-12-14