[Touch-packages] [Bug 1570587] Re: [FFe] Please update to bugfix release 20.7

2016-04-16 Thread Adam Conrad 
** Changed in: python-setuptools (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1570587

Title:
  [FFe] Please update to bugfix release 20.7

Status in python-setuptools package in Ubuntu:
  Fix Released

Bug description:
  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 `_
and Travis CI for continuous deployment.
  * Project versioning semantics now follow
`semver `_ 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 `_
from `Bitbucket `_.
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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570587] Re: [FFe] Please update to bugfix release 20.7

2016-04-14 Thread Martin Pitt 
This is a good rationale, the changelog sounds sane. I reviewed the diff
and most of it is documentation shuffling. The actual code changes are
not that big and have good test coverage. So while this is a central and
critical package I think the risk is bearable.

Approved and accepted the upload, thanks!

** Changed in: python-setuptools (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1570587

Title:
  [FFe] Please update to bugfix release 20.7

Status in python-setuptools package in Ubuntu:
  Fix Committed

Bug description:
  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 `_
and Travis CI for continuous deployment.
  * Project versioning semantics now follow
`semver `_ 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 `_
from `Bitbucket `_.
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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570587] Re: [FFe] Please update to bugfix release 20.7

2016-04-14 Thread Donald Stufft 
That is correct. For awhile now Python has had an adhoc concept of
environment markers, but there wasn't standard for what they were and
what they supported so each implementation was slightly different (this
is a common theme with Python packaging). We attempted to standardize
this in PEP 508 which was largely compatible with the primary
implementations but wasn't 100% compatible. setuptools 20.2 switched to
the new parser, which *only* supported PEP 508 markers and not any of
the older markers, which meant that anything that relied on one of the
cases that PEP 508 no longer supported was broken. The fixes since then
restore compatability with those, and continue to keep those old
projects installable. The regressions in 20.2 were fairly major.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1570587

Title:
  [FFe] Please update to bugfix release 20.7

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  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 `_
and Travis CI for continuous deployment.
  * Project versioning semantics now follow
`semver `_ 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 `_
from `Bitbucket `_.
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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570587] Re: [FFe] Please update to bugfix release 20.7

2016-04-14 Thread Barry Warsaw 
Yes, we want this in 16.04 so that the environment markers work
correctly.  My understanding is that without this, some packages can't
be properly installed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1570587

Title:
  [FFe] Please update to bugfix release 20.7

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  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 `_
and Travis CI for continuous deployment.
  * Project versioning semantics now follow
`semver `_ 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 `_
from `Bitbucket `_.
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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp