- Add options -l/--lazy, -O.

    - 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.

if there are no other public modules available

site-packages directories and use the right interpreter instead of raising
KeyError

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

(and more verbose in --verbose mode)

it's not in a list of supported Python versions (closes: 600529)

  * 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

    on the python version.

* Use versioned interpreter name rather than "python" only in python-minimal.postinst (closes: 595826)
* ducument how to regenerate dist_fallback file

    versions.

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))

(due to missing runpy module)

    Adam D. Barratt)

dh_python2: pass shallow=False to cmpfiles to make sure only exactly the same files are moved to pyshared