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
sage should *never* ever import numpy by default on startup. Yet again it does! #6494
Comments
Attachment: trac_6494.patch.gz |
Author: Mike Hansen |
comment:1
I don't think you can cimport numpy without causing an import in the module. Thus, a number of things have to be lazily imported. This will cause a problem if people do
since TimeSeries will be a LazyImport object rather than a class. I'm not sure the best thing to do, but I've posted a patch anyway. |
comment:2
numpy recently has made great improvements in its import speed, so maybe this isn't quite the issue it used to be? |
comment:4
I'm not going to judge whether numpy imports are still an issue or not, but in any case the patch needs to be rebased:
|
This comment has been minimized.
This comment has been minimized.
comment:5
This ticket is invalid now as all of the changes appearing in it are already in the Sage library. |
comment:6
You shouldn't just close tickets, leave that to the release manager. |
Reviewer: Mike Hansen |
Changed author from Mike Hansen to none |
I think this is because of the new complex_plot module, which I think I positively reviewed, so this is my fault. To resolve this ticket, make that import sufficiently lazy. Also, make a doctest that verifies that numpy is not imported when Sage starts up.
CC: @williamstein @jasongrout @robertwb
Component: packages: standard
Reviewer: Mike Hansen
Issue created by migration from https://trac.sagemath.org/ticket/6494
The text was updated successfully, but these errors were encountered: