Version does not conform to PEP440

[Václav Šmilauer]

When looking for available python modules, pkg_resources issues the following warning:

    /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:2512: PEP440Warning: 'python-apt (0.9.3.11build1)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.

The package version should be conforming.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: python-apt 0.9.3.11build1
ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15
Uname: Linux 3.13.0-46-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Apr 19 18:00:31 2015
SourcePackage: python-apt
UpgradeStatus: Upgraded to vivid on 2012-03-12 (1133 days ago)

[Scott Kitterman (kitterman)]

No. It shouldn't. Unfortunately, PEP-440 describes a versioning scheme that is incompatible with the versioning long used in Debian and it's derivatives such as Ubuntu. As the PEP says, "The main reason to even have a standardised version scheme in the first place is to make it easier to do reliable automated dependency analysis." We already have another system to do that and python-apt is conforming to it.

If one were to conform to PEP 440, then the package would be incompatible with distro versioning requirements.

Note: This is not general issue for Python packages. It is only a conflict for Debian/Ubuntu native packages like python-apt.

[Václav Šmilauer (eudoxos)]

Feel free to assign it to another package, but triggering warning in unrelated code just because the package is installed is definitely undesirable.

[Václav Šmilauer (eudoxos)]

Eh, I am not able to locate which part of code triggers the warning. In any case, debian version can be different from the one written in the .egg-info file (e.g. 0.9.3+11build1 is conforming to pep404, for instance).

[Scott Kitterman (kitterman)]

This warning ought to be suppressed. It's of interest to developers, not end users and in some cases wrong for Ubuntu packages anyway.

[Matthias Klose (doko)]

no, the warning is correct. python-apt shouldn't encode any nmu number or build number into it's own version string.

[Julian Andres Klode (juliank)]

It's basically irrelevant, is it not? We only use the setup.py for building, python-apt cannot be used by any of Python's package installation tools.

[Julian Andres Klode (juliank)]

This should do the trick:

http://anonscm.debian.org/cgit/apt/python-apt.git/commit/?id=165c3e534716c7f300a6419e2f0ccc331f63c0c9

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-apt - 1.0.0~beta3

---------------
python-apt (1.0.0~beta3) unstable; urgency=medium

  * tests/test_paths.py: Catch and assert the DeprecationWarning
  * setup.py: If no version is in the environment, return None
  * doc/source/library/apt_pkg.rst: Fix an example from old API to new API
  * apt.cache.FilteredCache: Fix multi-arch package lookups
  * apt.Cache: Introduce a connect2() callback connector
  * Break the FilteredCache <-> Cache reference cycle
  * apt.Cache: Issue a RuntimeWarning in connect()
  * doc: whatsnew: Document what's new in beta3

 -- Julian Andres Klode <email address hidden> Wed, 17 Jun 2015 18:28:44 +0200

[Muelli (ubuntu-bugs-auftrags-killer)]

Are we going to see this fix backported to, say, 15.04?

[Julian Andres Klode (juliank)]

It's backported in git already, we just need to get a permission to upload and upload it.