#8713: Prepare the ground for moving Parent._an_element_ to Sets().ParentMethods
---------------------------------+------------------------------------------
Reporter: nthiery | Owner: nthiery
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.4
Component: categories | Keywords: an_element
Author: Nicolas M. Thiéry | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------------+------------------------------------------
Changes (by nthiery):
* status: new => needs_review
* type: defect => enhancement
* milestone: => sage-4.4
Old description:
> As stated in the documentation of Parent._an_element_, this method
> need not be blazingly fast since an_element is cached anyway. Also,
> having it implemented in Parent, rather than in the categories makes
> it impossible for categories to override this default implementation
> with something more meaningful. Therefore it would be best moved to
> the ParentMethods of Sets().
>
> This first patch is a step in that direction. It just makes
> _an_element_ a def method rather than a cpdef method. This little
> change by itself causes the recompilation of a big part of Sage, which
> makes it completely impractical to work on a patch containing it (or
> in a patch queue containing it). So it would be nice to have this
> patch merged in Sage 4.4, so that we can start working comfortably on
> the moving of _an_element_ once it has been merged in.
New description:
As stated in the documentation of Parent._an_element_, this method
need not be blazingly fast since an_element is cached anyway. Also,
having it implemented in Parent, rather than in the categories makes
it impossible for categories to override this default implementation
with something more meaningful. Therefore it would be best moved to
the ParentMethods of Sets().
This first patch is a step in that direction. It just makes
_an_element_ a def method rather than a cpdef method. This little
change by itself causes the recompilation of a big part of Sage, which
makes it completely impractical to work on a patch containing it (or
in a patch queue containing it). So it would be nice to have this
patch merged in Sage 4.4, so that we can start working comfortably on
the moving of _an_element_ once it has been merged in.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8713#comment:1>
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.
