New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: <module 'setuptools.command.egg_info' from '/usr/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/setuptools/command/egg_info.pyc'> has no 'write_setup_requirements' attribute #356
Comments
Original comment by bradchoate (Bitbucket: bradchoate, GitHub: bradchoate): I came here to file this very ticket. |
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): The issue is unrelated to Python 3, but related to which version of setuptools is used to upgrade setuptools. I'm pretty sure I have environments that will encounter this error as well. The underlying issue is that setuptools prior to 10.0 cannot upgrade to 12.4 or later. I failed to fully grasp this requirement, or I would have more carefully advertized the change and made the release more cautiously. @richardipsum I'll probably have to back out this PR again, because there are a great number of setuptools environments that get created with old versions of setuptools (primarily by older versions of virtualenv). I'd like to propose that clients devise a means to work around this issue, forcing upgrades of the underlying setuptools versions or requiring two-step upgrades (upgrade to 12.3 then to 12.4+), but I'm not sure what the implications of that would be. @bradchoate, @bbbco Given this information, how much impact would it be to work around the issue until such a time that it's no longer relevant? |
Original comment by zroadhouse-rmn (Bitbucket: zroadhouse-rmn, GitHub: Unknown): +1 on backing out the PR. We have many systems where deployment (at the virtualenv step) is broken because of the 12.4 release. Edit: upgrading virtualenv (pip install --upgrade virtualenv) fixes the problem on our older servers. |
Original comment by bbbco (Bitbucket: bbbco, GitHub: bbbco): Any advice on how to only use setuptools 12.3? The problem comes when activating virtualenv which always retrieves the latest version of setuptools. If we can pass an ENV or a parameter that will indicate only use 12.3 for now, that shouldn't be a problem. |
Original comment by phaseburn (Bitbucket: phaseburn, GitHub: phaseburn): I also ran into this problem. Jenkins + OSX 10.8 build slave + virtualenv caused this exact same issue for me. I resolved it by upgrading setuptools manually via the ez_setup script, installing virtualenv again via that, and removing the old links to easy_install from the former version in /usr/bin (which OSX kindly put there from a very antiquated version), letting it fall back on the /usr/local/bin new ones. This should get people working again. I will say that I also +1 backing out of the PR due to the manual intervention of things, as this was a major issue that it just arbitrarily stopped working. I'm going to have to manually review all my build slaves tomorrow to make sure they aren't going to run into this same issue in the event we utilize them with a python virtualenv job. |
Original comment by lep (Bitbucket: lep, GitHub: lep): FYI I had the same problem with a buildout, were an old bootstrap.py pulled setuptools 0.7.2 and then running bin/buildout, the update to 12.4 failed. Bumping bootstrap.py to the latest version (that pulls a recent setuptools to start with) fixed the problem for me. Thanks! |
Original comment by katsuyan (Bitbucket: katsuyan, GitHub: Unknown): +1 For now, I have fixed setuptools version to 12.3 If you are using the latest bootstrap.py, here is how I fixed it:
|
any updates? |
Originally reported by: bbbco (Bitbucket: bbbco, GitHub: bbbco)
We are using setuptools on several Jenkins jobs in our environment. Yesterday, jobs ran fine. Today, some of them are failing while installing setuptools on a Python 2.7 environment. It now throws this error:
I have tracked it down to this recent commit. https://bitbucket.org/pypa/setuptools/commits/8bff4399a7af3d4d41d437248691f99818d1babd
This is an issue because we require the use of setuptools, but are not yet ready to upgrade python to python 3.
The text was updated successfully, but these errors were encountered: