#14187: Check that lazy imports are not resolved during startup
--------------------------------+-------------------------------------------
Reporter: vbraun | Owner: tbd
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.8
Component: performance | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Nicolas M. Thiéry
Authors: Volker Braun | Merged in:
Dependencies: #12543 | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by vbraun):
As you already said, time is about the time for a gc run:
{{{
sage: def lazy_test():
....: ns = dict()
....: lazy_import("sage.rings.semirings.all", "NN", "foo",
namespace=ns)
....: ns['foo']._get_object()
sage:
sage: %timeit lazy_test()
10 loops, best of 3: 54.1 ms per loop
}}}
I don't think we actually need the gc call, I just stuck it in there for
reproducability.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14187#comment:35>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
