-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
MNT: drop 3.5 testing for 3.1 branch #12538
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
Conversation
The 3.5 test was pinning all of the minimum deps, we need to move those over to one of the other tests. |
dist: trusty | ||
# pytest-cov>=2.3.1 due to https://github.com/pytest-dev/pytest-cov/issues/124. | ||
env: | ||
- PINNEDVERS='-c requirements/testing/travis35.txt' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also remove this file (or rename it to be the 3.6 pins).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were pinning numpy to 1.10 on the other builds?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the Travis 3.6 build was getting reqs from travis_all.txt, so I think this is OK... Oh duh, I see we need to make sure one of the tests tests the minimums. OK. Thats a bit more work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, see new file. I'm not sure if the other pinned reqs in travis35.txt were required to get it to run on 3.5 or if they were min deps we were wanting to test. I suspect the former, so I removed them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pytest and sphinx are pinned as minimum deps also.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is that? Are we testing that devs can use old Sphinx and pytest? Or are those user facing pins?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose so; those are the versions we specify in the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, - wasn't sure if w need the pin on pytest-timeout so trying w/o
Looks done to me, but let me know if I missed something! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to be the one to merge this so abuse the the 'request changes' feature to that end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
pandas<0.21.0 | ||
pytest==3.6 | ||
pytest-cov==2.3.1 | ||
# pytest-timeout==1.2.1 # Newer pytest-timeouts don't support pytest 3.4. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be removed instead of uncommented.
28352de
to
2ad5f6e
Compare
Sorry @timhoffm and @tacaswell - I messed up the rebase and had to do again. Clearing your approvals pending a new quick re-review |
stale after bad rebase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
travis36minver.txt
is missing
2ad5f6e
to
09ce51d
Compare
Should there be a |
Fixed now - sorry for the confusion! |
@@ -121,39 +121,6 @@ jobs: | |||
name: "Deploy new docs" | |||
command: ./.circleci/deploy-docs.sh | |||
|
|||
docs-python35: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's move to a 3.7 docker build, and pin numpy 1.11 on the 3.6 build?
The CircleCI build does complement the coverage of the test suite.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely, but does doing it on 3.6 and 3.7 buy us that much?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test with oldest numpy (1.11) on 3.6, latest on 3.7.
@@ -0,0 +1,6 @@ | |||
# Extra pip requirements for the first travis python 3.6 build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to delete travis35.txt no?
7590697
to
6a6f414
Compare
pushed one more commit to (I think) get the circle 37 job to actually run! |
Thanks @tacaswell. Not sure I understand the codecov complaint... |
I wonder if the azure |
As mentioned on the call we need to look at moving all the tests over to azure so I'm less worried about getting it's pinnings right yet. |
In |
Fixed |
0031c6c
to
85eef19
Compare
Fixed itself 😉 |
PR Summary
As per dev-list email, dropping 3.5 tests from Appveyor and Travis...
Feel free to push or close this if I did it incorrectly!
Probably todo is Circle-ci. Do we want to add 3.7 to that?
PR Checklist