Oh! I see. I think I interpreted as "this would be a good utility module". Small misunderstanding.
Even so, the mechanisms that cause Django to prompt for interaction are within that method. To make another method to me indicates overriding the one I just modified. But it's as I said I've only just begun using Django so I'm not very well versed in how the community prefers to tackle these problems. So I'd still like to hear how others would approach this. I think that many others must have encountered this issue (especially during automatic deployments) so it'd be good to see how they've gotten around this. Thanks. On Monday, May 25, 2015 at 6:23:24 PM UTC-7, Tim Graham wrote: > > My suggestion wasn't that update_contenttypes() couldn't be modified, but > rather that it might be better to expose the desired functionality as a > separate utility method to avoid having to explain in the documentation how > the interactive and force_remove keywords interact (probably the utility > method wouldn't need to allow the user to customize either of these). > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/73ef60fb-28b8-41d5-b493-165c207d3c39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
