#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 tscrim):

 Replying to [comment:9 vbraun]:
 > Replying to [comment:8 jdemeyer]:
 > > You are making the mistake that everything which has a `parent()`
 method is an `Element` of some `Parent`.
 >
 > If it walks like a duck and talks like a duck then it must be a duck.

 The issue to me is that `SageObject` walks and talks pretty close to a
 duck, but it is just a hunter with a toy duck trying to lure you in. I
 agree with Volker in comment:2 that we should strip `parent` out of
 `SageObject`. Also the `TestSuite` checks currently for idempotent-ness
 (but IDK if that needs to be a subclass of `Parent`).

 While we are at it, could we also do some of the others like `base_ring`
 and `n`?

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