#14767: Fix import_statements for lazy imported objects
-------------------------------------+--------------------------------------
Reporter: tmonteil | Owner: jason
Type: defect | Status: needs_info
Priority: major | Milestone: sage-5.11
Component: misc | Resolution:
Keywords: days49 | Work issues: Do we want the bonus
feature
Report Upstream: N/A | Reviewers: Nicolas M. Thiéry
Authors: Vincent Delecroix | Merged in:
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by nthiery):
Replying to [comment:7 vdelecroix]:
> I am not an expert of the lazy import buisness, but I do not want an
> extra layer on the objects I import. If I use a standard import
> statement inside a module it will neither affect the global
> namespace nor the starting time, right ?
Assuming your module is lazy imported, yes.
So your point is that, if a module is lazy imported (which should
progressively become the case most of the time), then within it the
modules it depends upon may as well be imported rather than lazy
imported. Ok, this sounds fair enough!
So positive review assuming the patchbot goes green.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14767#comment:8>
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.
