Package: python2.7 Version: 2.7.15-4 Severity: normal Recently, the version number of the Python 2.7 package appears to have been changed to "2.7.15+". I've experienced trouble with tools not accepting this as a valid version number. In particular, the popular tool "pipenv" relies on a library called "pythonfinder" which rejects "2.7.15+" as a valid version number, rendering pipenv unusable.
I am no expert in Python version numbering but PEP 0440 describes the format for version numbers. While "+" is mentioned in this PEP as a way to add a local version label, I believe the document assumes that the plus is followed by some non-empty string. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python2.7 depends on: ii libpython2.7-stdlib 2.7.15-4 ii mime-support 3.61 ii python2.7-minimal 2.7.15-4 python2.7 recommends no packages. Versions of packages python2.7 suggests: ii binutils 2.31.1-7 pn python2.7-doc <none> -- no debconf information
