#17437: integer arrays
-------------------------------------+-------------------------------------
Reporter: amri | Owner: amri
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.5
Component: combinatorics | Resolution:
Keywords: integer arrays | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/amri/integer_arrays | c8d93b37bcc758ee840a3ae26ba47de0ff8a5796
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:11 tscrim]:
> I was thinking this module would be lazily imported. However as soon as
you want to construct an element of the parent, it would trigger the numpy
import, and I'm wondering if you think it is worth the (relatively) large
import and using a large complicated (at least I imagine it is) class for
~20 lines of code?
Yes, the `numpy` import is worth it.
First of all, you mention "20 lines of code", but that's the current code.
Probably somebody will eventually want to enlarge the functionality or
will want to speed up the code, possibly duplicating more and more stuff
that's already done.
Second, importing `numpy` isn't that bad. Importing `numpy` is still
faster than importing all of Sage in the first place.
--
Ticket URL: <http://trac.sagemath.org/ticket/17437#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
