Skip to content
Snippets Groups Projects
Commit a39cbaa5 authored by Scott Kitterman's avatar Scott Kitterman
Browse files

* Python policy:

    - Add deprecation information about python-central and python-support
    - Clarify Python module and package descriptions
parent 5bff2ec3
No related branches found
No related tags found
No related merge requests found
...@@ -32,7 +32,12 @@ python-defaults (2.7.2-2) UNRELEASED; urgency=low ...@@ -32,7 +32,12 @@ python-defaults (2.7.2-2) UNRELEASED; urgency=low
- "--namespace foo" no longer triggers .../dist-packages/bar/foo/__init__.py - "--namespace foo" no longer triggers .../dist-packages/bar/foo/__init__.py
creation, use "--namespace bar.foo" instead creation, use "--namespace bar.foo" instead
-- Piotr Ożarowski <piotr@debian.org> Sun, 12 Jun 2011 13:28:48 +0200 [ Scott Kitterman ]
* Python policy:
- Add deprecation information about python-central and python-support
- Clarify Python module and package descriptions
-- Scott Kitterman <scott@kitterman.com> Thu, 07 Jul 2011 01:06:08 -0400
python-defaults (2.7.2-1) experimental; urgency=low python-defaults (2.7.2-1) experimental; urgency=low
......
...@@ -32,7 +32,7 @@ ...@@ -32,7 +32,7 @@
<name>Scott Kitterman</name> <name>Scott Kitterman</name>
<email>scott@kitterman.com</email> <email>scott@kitterman.com</email>
</author> </author>
<version>version 0.9.3.0</version> <version>version 0.9.4.0</version>
<abstract> <abstract>
This document describes the packaging of Python within the This document describes the packaging of Python within the
...@@ -371,18 +371,15 @@ ...@@ -371,18 +371,15 @@
<p> <p>
The goal of these policies is to reduce the work necessary for The goal of these policies is to reduce the work necessary for
Python transitions. Python modules are internally very Python transitions. Python modules are internally very
dependent on a specific Python version. However, we want to dependent on a specific Python version. These policies encourage
automate recompiling modules when possible, either during the automated dependency generation and loose version bounds whenever
upgrade itself (re-byte-compiling pyc and pyo files) or shortly possible.
thereafter with automated rebuilds (to handle C
extensions). These policies encourage automated dependency
generation and loose version bounds whenever possible.
<sect> <sect>
<heading>Types of Python Modules</heading> <heading>Types of Python Modules</heading>
<p> <p>
There are two kinds of Python modules, "pure" Python There are two kinds of Python modules, "pure" Python
modules, and extension modules. Pure Python modules are modules, and extension modules. Pure Python modules are
Python source code that works across many versions of Python source code that generally works across many versions of
Python. Extensions are C code compiled and linked against a Python. Extensions are C code compiled and linked against a
specific version of the python runtime, and so can only specific version of the python runtime, and so can only
be used by one version of Python. be used by one version of Python.
...@@ -393,8 +390,8 @@ ...@@ -393,8 +390,8 @@
linked to libpython. linked to libpython.
</p> </p>
<p> <p>
Python packages are directories containing at least a Python packages are either files or directories containing at least
<file>__init__.py</file>, other modules, extensions and a <file>__init__.py</file>, other modules, extensions and
packages (A package in the Python sense is unrelated to a packages (A package in the Python sense is unrelated to a
Debian package). Python packages must be packaged into the Debian package). Python packages must be packaged into the
same directory (as done by upstream). Splitting components same directory (as done by upstream). Splitting components
...@@ -731,6 +728,17 @@ Build-Depends: python3-all-dev (>= 3.1) ...@@ -731,6 +728,17 @@ Build-Depends: python3-all-dev (>= 3.1)
versa). This appendix is just an overview. If you use these versa). This appendix is just an overview. If you use these
tools, you should read their full documentation. tools, you should read their full documentation.
</p> </p>
<sect id="dh_python2_3">
<heading>dh_python2 and dh_python3</heading>
<p>
dh_python2 and dh_python3 are <package>debhelper</package> extensions
provided as part of Python and Python3 to make it easier to package
Python modules and extensions. They calculate Python dependencies, add
maintainer scripts to byte compile files, etc. Their use is not
mandatory, but they are recommended by the Python maintainers.
See man dh_python2 or man dh_python3 for details.
</p>
<sect id="distutils"> <sect id="distutils">
<heading>distutils</heading> <heading>distutils</heading>
<p> <p>
...@@ -773,9 +781,9 @@ Build-Depends: python3-all-dev (>= 3.1) ...@@ -773,9 +781,9 @@ Build-Depends: python3-all-dev (>= 3.1)
<sect id="pysupport"> <sect id="pysupport">
<heading>python-support</heading> <heading>python-support</heading>
<p> <p>
The python-support system provides a simple way to python-support is deprecated. It was system intended to provide
byte-compile pure Python modules and manage dependencies. It a simple way to byte-compile pure Python modules and manage dependencies.
integrates with <package>debhelper</package>, manages It integrates with <package>debhelper</package>, manages
byte-compilation, private modules, will properly use the byte-compilation, private modules, will properly use the
/usr/share/pyshared directory, integrates with runtime update /usr/share/pyshared directory, integrates with runtime update
hooks, and will fill-in the <tt>${python:Depends}</tt>, hooks, and will fill-in the <tt>${python:Depends}</tt>,
...@@ -790,9 +798,9 @@ Build-Depends: python3-all-dev (>= 3.1) ...@@ -790,9 +798,9 @@ Build-Depends: python3-all-dev (>= 3.1)
<sect id="pycentral"> <sect id="pycentral">
<heading>python-central</heading> <heading>python-central</heading>
<p> <p>
python-central provides another way to manage Python modules. It python-central is deprecated. It provided another way to manage
integrates with <package>debhelper</package>, manages Python modules. It integrates with <package>debhelper</package>,
byte-compilation, private modules, will properly use the manages byte-compilation, private modules, will properly use the
/usr/share/pyshared directory, integrates with runtime update /usr/share/pyshared directory, integrates with runtime update
hooks, and will fill-in the <tt>${python:Depends}</tt>, hooks, and will fill-in the <tt>${python:Depends}</tt>,
<tt>${python:Versions}</tt>, and <tt>${python:Provides}</tt> <tt>${python:Versions}</tt>, and <tt>${python:Provides}</tt>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment