8000 MAINT: Constrain `pip` and `setuptools` versions (Python 3.2 support) (NumPy 1.9.x Backport) by jakirkham · Pull Request #7080 · numpy/numpy · GitHub
[go: up one dir, main page]
Skip to content

MAINT: Constrain pip and setuptools versions (Python 3.2 support) (NumPy 1.9.x Backport) #7080

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

MAINT: Constrain pip and setuptools versions (Python 3.2 support) (NumPy 1.9.x Backport) #7080

wants to merge 3 commits into from

Conversation

jakirkham
Copy link
Contributor

Related: #6350

Appears that pip 8.0.0 and setuptools 19.0 drop Python 3.2 support, which is causing those builds to fail. This constrains them so that appropriate versions with Python 3.2 support will be installed.

Not sure this is necessary as several releases of 1.10.x are out, 1.11.x is being prepared, and 1.12.x is in development. Just in case it is.

@charris
Copy link
Member
charris commented Jan 21, 2016

Seems to have some problems.

@jakirkham
Copy link
Contributor Author

Agreed. Seems to be unrelated to this change. It fails to install apt-get dependencies.

jakirkham
jakirkham reviewed Jan 21, 2016
View reviewed changes
.travis.yml
@@ -38,7 +38,7 @@ before_install:
- pip install nose
# pip install coverage
- python -V
- pip install --upgrade pip setuptools
- pip install --upgrade "pip<8.0.0" "setuptools<19.0"
- pip install --find-links http://wheels.astropy.org/ --find-links http://wheels2.astropy.org/ --use-wheel Cython
- sudo apt-get install -qq libatlas-dev libatlas-base-dev gfortran
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the line where it fails.
8000

@jakirkham
Copy link
Contributor Author

Ok, with a few simple changes I think this will work. Seems it is just some changes to Travis CI's infrastructure that have caught up with us.

@jakirkham
Copy link
Contributor Author

Something is broken with the chroot environment. Not sure what it is.

@charris
Copy link
Member
charris commented Jan 21, 2016

Ah, you jogged my memory. Yes, travis has moved to the Amazon cloud and that broke the old scripts. I had to backport .travis.yml from master to 1.10.x to get it working. Probably not worth the effort unless Matthew pursues a 9.4 release.

@jakirkham
Copy link
Contributor Author

Yeah, that was the only reason I started doing this backport, but I agree. Let's see if 1.9.4 is going to happen and then this can be resumed. If not, then this can probably be closed out.

@jakirkham
Copy link
Contributor Author

@matthew-brett, are you still planning a 1.9.4 release? If so, we might need to backport the Travis test suite from 1.10.x.

@matthew-brett
Copy link
Contributor

I wasn't planning to do a release unless someone has a specific need for it.

@jakirkham
Copy link
Contributor Author

Thanks for clarifying.

In any event, backporting from the 1.10.x Travis CI tests will include this fix and is needed anyways. I don't want to embark on that unless we actually are planning another 1.9.x release. So, I'm going to close this out.

@jakirkham jakirkham closed this Jan 21, 2016
@jakirkham jakirkham deleted the pin_pip branch January 21, 2016 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
03 - Maintenance 05 - Testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@jakirkham @charris @matthew-brett
0