I believe the purpose of this class was to make it easier to remove the assumptions from the core. I would dig into the pull request and commits that introduced it to see if there is more information. I agree it's weird to have BasicMeta be both the metaclass and the superclass.
Aaron Meurer On Tue, Mar 10, 2015 at 4:46 AM, Joachim Durchholz <[email protected]> wrote: > ManagedProperties is declared like this: > > class ManagedProperties(with_metaclass(BasicMeta, BasicMeta)): > ... > > I.e. ManagedProperties has BasicMeta both as its metaclass and as its > superclass (so it is a metaclass itself). > > What's the purpose of this construction? > I suspect we should separate the metaclass functionality into a separate > class (or class hierarchy), but it's quite possible that I'm overlooking > something. > > (Once I know the purpose, I can analyze how it applies to subclasses which > have a similarly dual superclass-metaclass nature.) > > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/54FEBD76.40302%40durchholz.org. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6L%3Dsq9mG9AwuV3KzSYnA_D66X%3D_Fy4q620GK%3DxZHRQwQg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
