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
upgrade numpy to 1.12.1 #22895
Comments
comment:1
a branch is coming in a minute |
This comment has been minimized.
This comment has been minimized.
Author: Dima Pasechnik |
Commit: |
New commits:
|
Branch: u/dimpase/numpy1121 |
comment:4
The upgrade to numpy is included as part of #22582, which is already positively reviewed. So I propose to close this as a duplicate. |
Changed author from Dima Pasechnik to none |
Changed branch from u/dimpase/numpy1121 to none |
comment:5
I concur. |
Reviewer: Travis Scrimshaw |
Changed commit from |
comment:6
sure, no problem --- finding out that #22582 does a numpy update wasn't really possible. |
comment:7
Closing tickets in the sage-duplicate/invalid/wontfix module with positive_review (i.e. someone has confirmed they should be closed). |
this removes one of our patches, has more vectorisation, and in view of work on #22799 it's better to work with the latest release, to be in sync with numpy devs.
the tarball is here - more precisely it's a zip file.
CC: @kiwifb @jdemeyer
Component: packages: standard
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/22895
The text was updated successfully, but these errors were encountered: