#11943: The category graph should comply with Python's method resolution order
-----------------------------------------------------------------------------------------------------------+
Reporter: SimonKing
| Owner: nthiery
Type: enhancement
| Status: needs_work
Priority: major
| Milestone: sage-4.7.3
Component: categories
| Keywords: category graph, method resolution
order
Work_issues: Preserve super_categories etc. as methods, but introduce a lazy
attribute _super_categories | Upstream: N/A
Reviewer:
| Author: Simon King
Merged:
| Dependencies: #11900
-----------------------------------------------------------------------------------------------------------+
Changes (by SimonKing):
* status: needs_review => needs_work
* work_issues: => Preserve super_categories etc. as methods, but
introduce a lazy attribute
_super_categories
Comment:
[http://groups.google.com/group/sage-
devel/browse_thread/thread/ab03a0d422810e73 Maarten] suggested the
following:
{{{
What I think would be the best solution in this case would be is:
make lazy attributes
_super_categories and
_all_super_categories
Make the functions super_categories and all_super_categories say in the
documentation that developers shouldn't use these but that they should use
the lazy attributes.
}}}
I think that this would be a very good solution indeed.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:10>
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.
