Having Ring derive from parent_old.Parent was the intermediate state Robert put in after Dev Days 1 so that we could gradually transition rings to the new coercion model (after deciding doing the whole transition in one step was a bad idea). Of course, it has been almost 5 years and we're not done transitioning.... David
On Thu, Feb 14, 2013 at 6:23 AM, Volker Braun <[email protected]> wrote: > Well *really* somebody should change Ring to not derive > from parent_old.Parent. Somebody used both old and new parents as base to > avoid having to do this. > > > On Thursday, February 14, 2013 1:15:24 PM UTC, Simon King wrote: >> >> sage: Ring.mro() >> [<type 'sage.rings.ring.Ring'>, <type >> 'sage.structure.parent_gens.**ParentWithGens'>, <type >> 'sage.structure.parent_base.**ParentWithBase'>, <type >> 'sage.structure.parent_old.**Parent'>, <type >> 'sage.structure.parent.Parent'**>, <type >> 'sage.structure.category_**object.CategoryObject'>, <type >> 'sage.structure.sage_object.**SageObject'>, <type 'object'>] >> >> I think it *is* recommended to use Ring, isn't it? >> > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" 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-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" 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-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
