I can't say for sure, but it seems to me that there is so much going on in the satchmo code that it is best *not* to use inheritance. It is probably much safer to make new "extension" models that are related to the Product model and then play with the admin options. I hope this changes in the future, 'coz inheritance is a heck of a lot nicer and also easier to extend. The same goes for Satchmo views ... mmmmm ... class-based views.
On Monday, 9 July 2012 10:49:30 UTC-4, Paul Walsh wrote: > > There seems to be conflicting views on inheriting the Product model in > Satchmo. > > This is confounded by the following text found on the page dedicated to > custom product models on the Satchmo site: > > "Using inheritance is currently not recommended, because it has some > issues when it is used without care. Some methods ofproduct.models.Product > currently > do not expect to find subtypes which inherit attributes and methods from > product.models.Product." > > I'd like to know what the current word is, and, what methods are > problematic exactly, if any. > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To view this discussion on the web visit https://groups.google.com/d/msg/satchmo-users/-/-4dYOKR-TbcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
