python-distutils-extra 2.22

Milestone information

Martin Pitt
Release registered:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon python-distutils-extra-2.22.tar.gz (md5, sig) release tarball 310
last downloaded 18 weeks ago
Total downloads: 310

Release notes 

This release does not have release notes.


View the full changelog

* Drop import of "commands"; unused, and does not exist in
  * DistUtilsExtra/command/ Use "in" operator instead of
    has_key(). It's more elegant and Python 3 compatible.
  * test/ Use Python3 compatible octal constant.
  * test/ Decode stdout/stderr result from subprocess from bytes to
    str, to work with Python3.
  * test/ Use whichever Python interpreter we got invoked with (using
    /proc/self/exe) instead of hardcoding "python". With that we can run the
    tests through python3 as well.
  * DistUtilsExtra/ Port from deprecated "compiler" module to current
    "ast" module.
  * test/ Only set PYTHONPATH if it isn't set already, so that we can
    override it from outside.
  * test/ Do not require that " clean -a" doesn't print
    anything to stderr; with Python 3.1 it now sends out warnings about
    nonexisting directories.
  * test/ Changed print statements to work with both Python 2 and 3.
  * DistUtilsExtra/command/ Drop unnecessary hashbang line.
  * test/ Filter out bogus errors about missing files which current
    Python 3 distutils spews out.
  * test/, Use python{,3}-{pkg-resources,httplib2} as
    external test modules instead of -xdg and -dateutil, since the latter are
    not available for Python 3 yet.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.