#14767: Fix import_statements for lazy imported objects
-------------------------------------+--------------------------------------
Reporter: tmonteil | Owner: jason
Type: defect | Status: positive_review
Priority: major | Milestone: sage-5.11
Component: misc | Resolution:
Keywords: days49 | Work issues:
Report Upstream: N/A | Reviewers: Nicolas M. Thiéry
Authors: Vincent Delecroix | Merged in:
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by nthiery):
Replying to [comment:13 tmonteil]:
> - on the other hand, developpers using this to modify Sage's source code
> should know that the module is currently only lazy imported. Indeed,
if
> they "hard" import the module, this will lose the benefits of related
> lazy imports in terms of startup time.
Maybe not an issue, since now Sage complains if a lazy imported module is
resolved at startup time. Ah but this might not be the case if the module
is imported through another path ...
Well, let's get this patch in and think about it for the future.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14767#comment:14>
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/groups/opt_out.
