thing else, in which case, they should bring their own
> field. Is there a way to do this, perhaps with metaclasses or something?
> The key thing being that it has to not muck up the Django machinery.
>
> (cross posted from
> http://stackoverflow.com/questions/15249306/django-co
eld. Is there a way to do this, perhaps with metaclasses or something?
The key thing being that it has to not muck up the Django machinery.
(cross posted from
http://stackoverflow.com/questions/15249306/django-conditionally-defined-model-field-in-abstract-model,
if you want to answer for po
(cross-posted from
StackOverflow<http://stackoverflow.com/questions/15249306/django-conditionally-defined-model-field-in-abstract-model>,
answer there if you prefer, but I thought it might be too low level to get
much help there alone)
I've got an abstract model in my project tha
3 matches
Mail list logo
