Hi Jeroen,
On Sat, Dec 09, 2017 at 09:44:54AM +0100, Jeroen Demeyer wrote:
> The "modern" way to define a Parent class is as follows:
>
> class MyParent(Parent):
> Element = MyElement
> def __init__(self):
> Parent.__init__(self, category=MyCategory())
>
> One thing which surprises me is that the code to have the "Element =
> MyElement" trick work is implemented in the category of Sets. It seems to me
> that this should really be part of the general Parent infrastructure,
> independent of categories.
>
> So, is there any particular reason why this is implemented in Sets? Are
> there any objections to changing that?
As far as I remember, it's stipulated that any Parent should be in
Sets. So, like for many other features, it's possible in principle to
implement them equivalently in Parent or Sets.ParentMethods. The
latter tends to be more flexible (e.g. a subcategory can override it).
Is there a use case where having this in Parent would be preferable?
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
