Public bug reported: In the upstream version v20.2 setuptools switched implementations of parser libraries. This is an internal implementation detail, however the new parser library did not correctly handle several edge cases which caused regressions preventing certain packages from installing or, in some cases, even running. These issues have been fixed upstream by versions v20.6.6 and v20.6.8. The changelog delta between what Ubuntu currently has an v20.7 looks like:
v20.7.0 ------- * Refactored extra enviroment marker processing in WorkingSet. * Issue #533: Fixed intermittent test failures. * Issue #536: In msvc9_support, trap additional exceptions that might occur when importing ``distutils.msvc9compiler`` in mingw environments. * Issue #537: Provide better context when package metadata fails to decode in UTF-8. v20.6.8 ------- * Issue #523: Restored support for environment markers, now honoring 'extra' environment markers. v20.6.7 ------- * Issue #523: Disabled support for environment markers introduced in v20.5. v20.6.6 ------- * Issue #503: Restore support for PEP 345 environment markers by updating to Packaging 16.6. v20.6.0 ------- * New release process that relies on `bumpversion <https://github.com/peritus/bumpversion>`_ and Travis CI for continuous deployment. * Project versioning semantics now follow `semver <https://semver.org>`_ precisely. The 'v' prefix on version numbers now also allows version numbers to be referenced in the changelog, e.g. https://pythonhosted.org/setuptools/history.html#v20-6-0. 20.5 ---- * BB Pull Request #185: Add support for environment markers in requirements in install_requires, setup_requires, tests_require as well as adding a test for the existing extra_requires machinery. 20.4 ---- * Issue #422: Moved hosting to `Github <https://github.com/pypa/setuptools>`_ from `Bitbucket <https://bitbucket.org/pypa/setuptools>`_. Issues have been migrated, though all issues and comments are attributed to bb-migration. So if you have a particular issue or issues to which you've been subscribed, you will want to "watch" the equivalent issue in Github. The Bitbucket project will be retained for the indefinite future, but Github now hosts the canonical project repository. As you can see, v20.4 simply adjusted documentation and some release scripts to deal with the migration from Mercurial+Bitbucket to Git+Github and should have little bearing on the actual project or have much potential for regression. The next version, v20.5 did add a new feature, but was later removed in v20.6.7. v20.6.0 is another release which largely just changed processed and documentation without any major code changes. v20.6.1-5 are nonexistent, v20.6.6 is a change we want, v20.6.8 is a change we want, and v20.7 is some minor bugfixes and a tiny bit of refactoring. You can see a diff here: https://launchpadlibrarian.net/253841863 /python-setuptools_20.3.1-1_20.7.0-1.diff.gz though it is deceptively larger than it actually is due to the rename of CHANGES.txt -> CHANGES.rst and some shuffling around of URLs and such in the documentation. ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570587 Title: [FFe] Please update to bugfix release 20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
