dh_python2

    - Don't over-optimize, check the timestamps of byte-code files.
    - Use the correct name for byte-code files.
    - Add an option -f/--force.
    - Copy stdout/stderr of py_compile processes in case of error.
    - Propagate the exit value of the py_compile processes.
    - Update manual page.
  * Bump depends to require the fixed pycompile for dh_python2 based package
    builds.
  * Don't touch the standard python library in rtupdate scripts.

as public modules for all requested Python versions (use dh_install's
package.install files for private modules)

  * Add python2.7 as a supported Python version.
  * python-all{,-dev,-dbg}: Depend on the 2.7 packages.
  * Run the rtinstall script, when 2.7 became a supported version (2.6.6-4)
    and python2.7 is installed.

 -- Matthias Klose <doko@debian.org>  Sat, 16 Oct 2010 11:58:31 +0200

fall back to package name recommended by Debian Python Policy (use
debian/pydist-override file to override)

(with a list of Python distribution name and Debian package name pairs (to be
used as a fall back source for PyDist feature))

(closes: 590224)

doesn't contain dependency that package needs)

dh_python2: follow Distribute and replace all non-alphanumeric characters with underscore in distribution name

    pycompile.

(Breaks will be used if available)

(hardcoding list of versions is evil anyway)

* add execute bit in rtupdate scripts

* ignore dh's -O option
* allow multiple -p options
* add -N option

(rather than replacing python2.6)

* fix -p option

* make sure pycompile binary is available at intall time
* do not require pyclean at uninstall time