#17694: zero vs zero_element / one vs one_element
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.5
Component: algebra | Resolution:
Keywords: | Merged in:
Authors: Vincent Delecroix | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vdelecroix/17694 | c0a0bbbe64c8524c98c88f342c62cc426c604260
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:7 jdemeyer]:
> The polyhedra change worries me (as potential reviewer) because I don't
fully understand how categories work.
For the purpose of this ticket, you only need to know that `ParentMethods`
and `ElementMethods` in the categories are respectively inherited to the
concrete `Parent` and `Element` (via a dirty mechanism of dynamic classes
created on the fly).
An other option is to revert the changes and add a
`deprecated_function_alias` inside the polyhedron class.
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/17694#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/d/optout.
