On 11/02/16 09:22, 'Hugo Osvaldo Barrera' via Django developers (Contributions to Django itself) wrote:
Hi there, I'd love to see some (most?) of the features from django-polymorphic on django itself. I'm very much be willing to work on this myself. Of course, there's several details that need to be discussed too, HOWEVER, but before I even start, I'd like to know if they'd even be acceptable in django, or, for some reason, the functionality has been kept out of django-core.
As I recall it, the general approach here is: is there a reason this can't live as a 3rd party app?
Would it benefit significantly by being more deeply integrated into core, and if so, does it bring sufficient benefit to users to warrant the changes?
There was some research by Sebastian Vetter on "single-child auto-resolve" solutions for MTI and how they scaled (from memory, model-utils' InheritanceManager, polymorphic, and generic-m2m) https://github.com/elbaschid/mti-lightbulb
-- Curtis -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/56BBE052.8000205%40tinbrain.net. For more options, visit https://groups.google.com/d/optout.
