I'm not sure. Did you find this past discussion: https://groups.google.com/d/topic/django-developers/tSLuqu0UFrY/discussion ? The idea was also mentioned a month ago with no replies: https://groups.google.com/d/topic/django-developers/Ov91x7AXwmM/discussion
Are you a maintainer of django-polymorphic? What's the advantage of bringing it into core as opposed to keeping it as an external project? This is the correct place for the discussion (non-trivial design decisions). On Wednesday, February 10, 2016 at 5:22:30 PM UTC-5, Hugo Osvaldo Barrera 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. > > Would a well designed PR to incorporate this be acceptable? Is it worth > opening a discussion? Or has this been rejected before, and my searching > skills failed me? > > Also on this topic; should this discussion be opened here, or rather as > an issue over at code.djangoproject.com? > > Thanks, > > -- > Hugo Osvaldo Barrera > -- 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/87e7c36b-d725-4efd-be4b-a2a035a90c3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
