On Saturday, October 13, 2012 10:35:10 AM UTC-7, Luke Plant wrote: > > Hi all, > > https://code.djangoproject.com/ticket/18054 > > I just came across this, and it seems slightly hasty. Most deprecations > of entire contrib modules would require some discussion on django-devs, > I would have thought. >
That seems entirely reasonable, but if it is the convention, I wasn't aware of it - sorry. The ticket got some relatively quick traction just in trac. This goes to the heart of defining the purpose, current and future, of contrib. I believe in shrinking in contrib - but I do think it has to be done mindfully. There was some *brief* conversation at DjangoCon about phasing contrib.markup out in a fashion similar to localflavor - but it seemed to end unresolved in a discussion of submodules, namespace, and other imperfect solutions. On this issue of markup I do think the answer should lie in a strong 3rd party option. I agree we could provide better migration docs and maybe we shouldn't do an accelerated deprecation to give a better migration option the chance to be developed? -Preston -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/xprtiUsPQv4J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
