#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 nbruin):
Replying to [comment:20 vbraun]:
> Just query the referrers to the lazy import, should be easy.
Do you mean `gc.get_referrers`? That should mainly get you a list of
dictionaries, indeed. You'd propose to just assume that those are
`globals` dictionaries and change the bindings? That sounds horribly hacky
and dangerous to me. Robert can probably comment on the wisdom of this.
There's also the question of how to change the referrers once you've found
them. For a dict that's straightforward, but what if you're finding a
tuple referring to it? Or a homomorphism instance? What if you're finding
a module that has decided to customize itself and has a frozendict as
namespace?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14187#comment:21>
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.
