#18026: Parent breakage because not every SageObject is idempotent
----------------------------+------------------------
       Reporter:  vbraun    |        Owner:
           Type:  defect    |       Status:  new
       Priority:  major     |    Milestone:  sage-6.6
      Component:  pickling  |   Resolution:
       Keywords:            |    Merged in:
        Authors:            |    Reviewers:
Report Upstream:  N/A       |  Work issues:
         Branch:            |       Commit:
   Dependencies:            |     Stopgaps:
----------------------------+------------------------

Comment (by vbraun):

 Replying to [comment:3 vdelecroix]:
 > And I would not call it a "parent class" since it is the class of the
 object itself that is considered as a parent. Which makes sense.

 No. Parent calls are idempontent, type calls are not.

--
Ticket URL: <http://trac.sagemath.org/ticket/18026#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 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.

Reply via email to