Hey all, I recently opened up a ticket (https://code.djangoproject.com/ticket/21081) that turns out to be a dupe of https://code.djangoproject.com/ticket/5793, both in regards to allowing custom attributes in a model's Meta class.
It was wontfix'd six years ago, the reasoning being that Meta should really only be for setting options related to Django internals. I'm personally of the opinion that at this point Meta is considered the place for *any* options related to a model by developers, and that handling custom options outside of Meta seems against the general Django coding style. Currently you can come up with hacks like https://github.com/karanlyons/django-save-the-change/blob/feature/update-together/save_the_change/mixins.py#L188 to take care of the issue, but this isn't very nice for a number of reasons. Do we think this should still be a wontfix, and are there any other reasons why? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
