Skip to content

[MRG] Remove Python < 3.5 from continuous integration #11995

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

Closed
wants to merge 2 commits into from
Closed

[MRG] Remove Python < 3.5 from continuous integration #11995

wants to merge 2 commits into from

Conversation

abbyeg
Copy link

@abbyeg abbyeg commented Sep 4, 2018

Reference Issues/PRs

Fixes #11989

What does this implement/fix?

Removes python versions 2/3.4 and lower from CI config files.

#### Reference Issues/PRs
Fixes #11989

#### What does this implement/fix? Removes python versions 2/3.4 and lower from CI config files.
- python-scipy
- libatlas3-base
- libatlas-dev
# Python 3.4 build
Copy link
Member

Choose a reason for hiding this comment

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

We still need a run with minimum requirements, so make sure that we have a python 3.5 run and that minimum / alternative variants of dependencies are still tested

Copy link
Author

Choose a reason for hiding this comment

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

Do you think it would be fine to update this to remove the python2 env, but change 3.4 to 3.5? It looks like we're only testing the 'ubuntu' distribution under python 2, so we could move that up to 3.5 as well, unless we don't want to support that going further?.

Copy link
Member

Choose a reason for hiding this comment

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

I think we still want to support Ubuntu LTS package distributions. Can you check whether trusty providers python 3.5+ with those same numpy/scipy releases?

@jnothman
Copy link
Member

jnothman commented Sep 4, 2018

Thanks for tackling this!

@rth
Copy link
Member

rth commented Sep 4, 2018

Just a note that this shouldn't be merged before the final 0.20 release, and I would argue we could even wait for 0.20.1 to make backports easier, as I'm not sure how many people actually test 0.20.rc1..

@jnothman
Copy link
Member

jnothman commented Sep 4, 2018 via email

- NUMPY_VERSION: 1.8.2
# XXX: plot_gpc_xor.py fails with scipy 0.13.3
- SCIPY_VERSION: 0.14
- MATPLOTLIB_VERSION: 1.3
Copy link
Member

Choose a reason for hiding this comment

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

I wonder whether we should continue to test support for matplotlib 1.x

- python-scipy
- libatlas3-base
- libatlas-dev
# Python 3.4 build
Copy link
Member

Choose a reason for hiding this comment

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

I think we still want to support Ubuntu LTS package distributions. Can you check whether trusty providers python 3.5+ with those same numpy/scipy releases?

@jnothman
Copy link
Member

jnothman commented Dec 3, 2018

I think we should do this now, but there have been changes to circle and travis configs that have caused merge conflicts, sorry @abbygrbl. You also haven't responded to #11995 (comment). Would you like someone else to take this issue?

@abbyeg
Copy link
Author

abbyeg commented Dec 8, 2018

Sorry about that, I will close this out.

@abbyeg abbyeg closed this Dec 8, 2018
@abbyeg abbyeg deleted the remove-py-versions-from-ci branch December 8, 2018 01:51
@jnothman
Copy link
Member

jnothman commented Dec 9, 2018

Hi @abbygrbl, we would be very happy if you would like to continue your work here. But it required changes before merge. I take it you would like someone else to complete it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove Python < 3.5 from continuous integration
3 participants