#11003: Improve support for lazy_import inside classes
---------------------------+------------------------------------------------
Reporter: nthiery | Owner: jason
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-wishlist
Component: misc | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: Mike Hansen
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by nthiery):
Replying to [comment:3 mhansen]:
> Replying to [comment:2 nthiery]:
> > What's the rationale for not always walking through the whole mro?
>
> Do you mean the break?
Sorry, I should have been more explicit. It's about the using
`owner.__bases__' rather than ``owner.__mro__''.
By the way, what about using ``owner.mro()'' to respect encapsulation?
Speed is not an issue here, right?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11003#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
