#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: | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by robertwb):
Replying to [comment:27 vbraun]:
> For the record, we are using `gc.get_referrers()` already in the Sage
library.
>
> The alternative is to walk `sys.modules` for lazy imports into modules
and fall back to what we have for class-level lazy imports.
>
> But at the end of the day lazy imports are a hack so why not have the
garbage collector do the work for us?
+1, I see this as a "best effort" kind of a thing anyways.
In terms of efficiency, I think it might make sense to try to attempt a
lookup before iterating over the (potentially very large) dict.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14187#comment:29>
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.
