#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 vdelecroix):
Replying to [comment:4 nthiery]:
> Replying to [comment:2 vdelecroix]:
> > I strongly disagree by putting lazy as True for lazy imported objects.
>
> What's your rationale? If something is lazy imported in the global
> name space, then it's likely that whoever needs it will want to lazy
> import it, no?
>
> The only drawback is that lazy imported classes are a bit more fragile
> due to the isinstance issue.
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 ?
> > The behavior is nevertheless corrected with a two line patch which
> > needs review (but the description of the ticket needs to be modified
> > accordingly if you agree with my solution).
>
> I'll have a look.
Many thanks!
Cheers,
Vincent
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14767#comment:7>
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.
