Skip to content
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

MNT: Drop support for numpy < 1.15.3 #3284

Merged
merged 1 commit into from
Mar 31, 2021
Merged

Conversation

effigies
Copy link
Member

Summary

We forgot to drop support for numpy < 1.14 for the last minor release, but the next NEP29+1y milestone is Jan 7 2021, and I doubt we'll have a minor release before then. This drops support for <1.15.3, which means we can drop our split between 3.6 and 3.7+ dependencies.

Acknowledgment

  • (Mandatory) I acknowledge that this contribution will be available under the Apache 2 license.

Copy link
Contributor

@oesteban oesteban left a comment

Choose a reason for hiding this comment

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

I think we need to keep special pinnings for PY36, although if we are to follow Numpy's schedule we can just drop PY36

# Numpy bug in python 3.7:
# https://www.opensourceanswers.com/blog/you-shouldnt-use-python-37-for-data-science-right-now.html
NUMPY_MIN_VERSION_37 = "1.15.3"
NUMPY_MIN_VERSION = "1.15.3"
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
NUMPY_MIN_VERSION = "1.15.3"
NUMPY_MAX_VERSION_36 = "1.20"
NUMPY_MIN_VERSION = "1.15.3"

@@ -138,8 +137,7 @@ def get_nipype_gitversion():
"click>=%s" % CLICK_MIN_VERSION,
"networkx>=%s" % NETWORKX_MIN_VERSION,
"nibabel>=%s" % NIBABEL_MIN_VERSION,
'numpy>=%s ; python_version < "3.7"' % NUMPY_MIN_VERSION,
'numpy>=%s ; python_version >= "3.7"' % NUMPY_MIN_VERSION_37,
'numpy>=%s' % NUMPY_MIN_VERSION,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
'numpy>=%s' % NUMPY_MIN_VERSION,
f'numpy>={NUMPY_MIN_VERSION},<{NUMPY_MAX_VERSION_36} ; python_version < "3.7"',
f'numpy>={NUMPY_MIN_VERSION} ; python_version >= "3.7"',

@effigies
Copy link
Member Author

effigies commented Jan 5, 2021

While it's not hard to support the edge case of people using Python 3.6 and setup.py and not already having numpy installed, it might be better to let deprecated use cases fail in order to prod people to update their practices. New users should not experience this, since the docs have instructed people to use pip install instead of easy_install or setup.py since 0.13.0 (#1977).

@effigies effigies merged commit 9e8b655 into nipy:master Mar 31, 2021
@effigies effigies added this to the 1.6.1 milestone May 1, 2021
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.

2 participants