#25068: Metaclass conflict when doing createmigrations in ModelState.render
-------------------------------------+-------------------------------------
Reporter: kosz85 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: metaclass conflict | Triage Stage:
createmigrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by kosz85):
I attached isolated case from my project. There is also version of
metaclassmaker that I use, it's same as in the link. I know that playing
with multiple inheritance and metaclasses is not so simple, but with
metaclassmaker it's also not a problem, and I get quite nice features at
model level like all subclasses (and subsubsubsub classes ) aware class
registry, or some class aware lists, and other magic tools.
With this one you can create all things like Notifications, LogTypes,
IndexableMixins, SyncMixins, ..., with automatic population of all ever
created classes of objects in nice and neat way.
--
Ticket URL: <https://code.djangoproject.com/ticket/25068#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.86fc763dc6163a165d85e6a92960c658%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
