#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 tscrim):
Replying to [comment:10 nbruin]:
> Replying to [comment:9 tscrim]:
> > In principle, I agree. However, do we really want to trigger an import
of (all of) numpy just to have an array with a few already built features
that are easy to redo?
>
> A lazy one? sure.
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?
--
Ticket URL: <http://trac.sagemath.org/ticket/17437#comment:11>
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.
