Adding a new meta option is very unlikely to happen.
Really, this is a question about dynamic choices, rather than just
inheritance. I'd rather see some sort of solution which allows some
(optional) hooks to customise choices on a per-class (or maybe even per
instance) basis. This is tricky though
>From the doc: "Abstract base classes are useful when you want to put some
common information into a number of other models". In my current project I
put all common fields in abstact class, but those fields that use 'choice'
option may have different choices in different child classes.
Code Exa
