tahoe-lafs/trac-2024-07-25

"UndefinedEnvironmentName" error with setuptools-20.6 #2762

New issue

Closed

opened 2016-03-31 05:06:56 +00:00 by warner · 1 comment

warner commented

2016-03-31 05:06:56 +00:00

Owner

https://github.com/pypa/setuptools/issues/523 is the setuptools bug. Apparently most 20.5.* and 20.6.* versions are broken. The recommended workaround (verified by warner and cypher) is to downgrade to setuptools-20.4, e.g.:

(venv) % pip install setuptools==20.4

The symptom is that pip install tahoe-lafs works normally, but then actually trying to run tahoe gives a traceback like the following:

  File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 278, in evaluate
    return _evaluate_markers(self._markers, current_environment)
  File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 203, in _evaluate_markers
    lhs_value = _get_env(environment, lhs.value)
  File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 185, in _get_env
    "{0!r} does not exist in evaluation environment.".format(name)
pkg_resources._vendor.packaging.markers.UndefinedEnvironmentName: 'extra' does not exist in evaluation environment.

I'm hoping that they'll make a new release tomorrow that fixes the problem, but in the meantime, if you see this error, try downgrading your setuptools.

The tahoe-1.11.0 release was only a few hours old when we started getting reports of failures. It looks like setuptools made a release today that breaks many packages. (In fact, they made seven releases today, which can't be a good sign). <https://github.com/pypa/setuptools/issues/523> is the setuptools bug. Apparently most 20.5.* and 20.6.* versions are broken. The recommended workaround (verified by warner and cypher) is to downgrade to setuptools-20.4, e.g.: ``` (venv) % pip install setuptools==20.4 ``` The symptom is that `pip install tahoe-lafs` works normally, but then actually trying to run `tahoe` gives a traceback like the following: ``` File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 278, in evaluate return _evaluate_markers(self._markers, current_environment) File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 203, in _evaluate_markers lhs_value = _get_env(environment, lhs.value) File "/ve/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.py", line 185, in _get_env "{0!r} does not exist in evaluation environment.".format(name) pkg_resources._vendor.packaging.markers.UndefinedEnvironmentName: 'extra' does not exist in evaluation environment. ``` I'm hoping that they'll make a new release tomorrow that fixes the problem, but in the meantime, if you see this error, try downgrading your setuptools.

tahoe-lafs added the

labels 2016-03-31 05:06:56 +00:00

tahoe-lafs added this to the undecided milestone 2016-03-31 05:06:56 +00:00

warner commented

2016-03-31 18:12:24 +00:00

Author

Owner

Setuptools-20.6.7 has fixed the problem (they reverted the change that triggered it, and will try again in some later release). So a newly-upgraded virtualenv ought to be ok now.

They've removed almost all of the broken versions from pypi: it is still possible to install 20.6.6 (which breaks for me), but 20.5 and 20.6.0-20.6.5 are no longer on pypi (which also means I can't easily test them to identify exactly which ones were broken).

So: if you see this problem, do a pip install --upgrade setuptools. If the problem persists and pip list reports a setuptools of 20.6.7 or later, please re-open this ticket and give us the details.

Setuptools-20.6.7 has fixed the problem (they reverted the change that triggered it, and will try again in some later release). So a newly-upgraded virtualenv ought to be ok now. They've removed almost all of the broken versions from pypi: it is still possible to install 20.6.6 (which breaks for me), but 20.5 and 20.6.0-20.6.5 are no longer on pypi (which also means I can't easily test them to identify exactly which ones were broken). So: if you see this problem, do a `pip install --upgrade setuptools`. If the problem persists and `pip list` reports a setuptools of 20.6.7 or later, please re-open this ticket and give us the details.

tahoe-lafs added

critical

fixed

and removed

major

labels 2016-03-31 18:12:24 +00:00

tahoe-lafs modified the milestone from undecided to soon (release n/a)

2016-03-31 18:12:24 +00:00

warner closed this issue

2016-03-31 18:12:24 +00:00