Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Remove workaround for numpy<1.16, and update version check.#19500
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
We now require numpy 1.16 (per setup.py and NEP29).
timhoffm commentedFeb 16, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Are these based on
? |
Yes, the setup.py versions of dateutil and pyparsing were both bumped in#17662 (to the oldest version that did not have deprecation warnings on py36 (I think importing without warnings is a defend-able definition of "support" because otherwise we would have to protect their imports to keep our tests passing). Seedd61ed1 andcfccfb8 for details. |
We now require numpy 1.16 (per setup.py and NEP29).
PR Summary
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).