Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Merged
timhoffm merged 3 commits intomatplotlib:masterfromanntzer:np116
Feb 16, 2021

Conversation

anntzer
Copy link
Contributor

We now require numpy 1.16 (per setup.py and NEP29).

PR Summary

PR Checklist

  • Has pytest style unit tests (andpytest passes).
  • IsFlake 8 compliant (runflake8 on changed files to check).
  • New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs shouldbuild without error).
  • Conforms to Matplotlib style conventions (installflake8-docstrings and runflake8 --docstring-convention=all).
  • New features have an entry indoc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented indoc/api/next_api_changes/ (follow instructions in README.rst there).

We now require numpy 1.16 (per setup.py and NEP29).
@anntzeranntzer added this to thev3.4.0 milestoneFeb 11, 2021
@tacaswell
Copy link
Member

Apparently I missed these in60b03f1 /#17662 and there is already an API note change included in that PR (which I noted after I helpfully pushed a commit to this branch to add one 🤦 ).

Also pushed a commit bumping the run-time version of pyparsing and dateutil.

@timhoffm
Copy link
Member

timhoffm commentedFeb 16, 2021
edited
Loading

Also pushed a commit bumping the run-time version of pyparsing and dateutil.

Are these based on

We will only bump these dependencies as we need new features or the old versions no longer support our minimum NumPy or Python.

?

@tacaswell
Copy link
Member

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.

timhoffm reacted with thumbs up emoji

@timhoffmtimhoffm merged commitd235b02 intomatplotlib:masterFeb 16, 2021
@anntzeranntzer deleted the np116 branchFebruary 16, 2021 08:41
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@QuLogicQuLogicQuLogic approved these changes

@timhoffmtimhoffmtimhoffm approved these changes

Assignees
No one assigned
Projects
None yet
Milestone
v3.4.0
Development

Successfully merging this pull request may close these issues.

4 participants
@anntzer@tacaswell@timhoffm@QuLogic

[8]ページ先頭

©2009-2025 Movatter.jp