-
-
Notifications
You must be signed in to change notification settings - Fork 11k
Backport 7131 #7132
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
Backport 7131 #7132
Conversation
The cause of the failing tests is likely this
Looks like we need later pip or setuptools, but they don't support 2.6,3.2, and 3.3. I'm inclined to remove the test from this backport. |
Maybe we just need an earlier virtualenv? |
(If these kinds of things continue to be a pain then it wouldn't be the end of the world to just drop 2.6/3.2/3.3 for 1.11. definitely it's nice to give people advance warning but getting stuck on 1.10 is not really any different than getting stuck on 1.11 for most people, I think.) |
Checking if things work apart from known fails with current setuptools and pip. @njsmith Has virtualenv changed recently? |
I'm just guessing based on the fact that it's the virtualenv call that's On Wed, Jan 27, 2016 at 3:31 PM, Charles Harris notifications@github.com
Nathaniel J. Smith -- https://vorpus.org http://vorpus.org |
Looks like virtualenv was upgraded about a week ago (14.0.0 & 14.0.1). |
9514547
to
3fd93d1
Compare
Just remove the commit with the test I'd say. There's not much value in backporting that. |
This was seriously broken. Setuptools does unwanted 'smart' things and ignores MANIFEST.in. Closes numpygh-7127.
Warn in numpy/distutils/command/egg_info.py if using setuptools.sdist. See numpygh-7127 for details.
3fd93d1
to
dae1a38
Compare
@rgommers I was going to remove the versioning and Python 3.2 test, but removing the sdist test is just as easy. |
Backport #7131, Fix setuptools sdist