#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 nthiery):
Replying to [comment:17 vbraun]:
> I disagree, imports are much more legible without the lazy_import call.
And being easy to read is more important than a nanosecond saved by
avoiding the lazy_import redirect.
A nanosecond multiplied by the number of times the object is used. Here
it's for example used in is_canonical which is a fairly low level method.
Also as much as I highly value readibility of code, as much I don't care
so much about the readibility of imports (but it's a pain that pyflakes
does not handle lazy imports).
Well, just my personal opinion; go ahead in either way you feel better.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14187#comment:18>
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.
