Le jeudi 03 mai, Simon King a écrit: > On the other hand: One could argue that the parent class can > expect that some basic tools (such as __hash__ and __repr__) already > work when being called. Hence, before calling __init__ of the parent > class, one is supposed to make sure that the "tool chain" is provided.
The parent class cannot expect anything if it's initialization code hasn't been called, can it? > And one could argue that a commutative algebra is, in the *first* > place, a commutative algebra, then in the *second* place it is an > algebra, which is a module and a commutative ring (which then is a > ring), which are parents. From that point of view, one would expect > that the initialisation goes from the most specific to the most > general - hence, *parallel* to the mro. No, a commutative algebra is first an algebra, and then has some additional properties. I never saw a book define them in the reverse order... > I simply don't know if there is any convention established (by that I > mean: Documented, and I'd like to see a link) among Python developers, > or at least among Sage developers. Beware of conventions among sage developers : prefer conventions which apply among many other opensource projects. Here are some links (the last one is about C++ but it's still interesting to know what is done elsewhere) : http://stackoverflow.com/questions/1385759/should-init-call-the-parent-classs-init http://stackoverflow.com/questions/6187042/inheritance-in-python-and-constructor-calls http://stackoverflow.com/questions/120876/c-superclass-constructor-calling-rules Snark on #sagemath -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
