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