On Fri, Oct 16, 2009 at 5:10 AM, Luke Plant <l.plant...@cantab.net> wrote: > I think this means that either the deprecation cycle would have to > pushed back one (i.e. pending deprecation warning in 1.3, deprecation > in 1.4, removed in 1.5), or core/contrib should be fixed by 1.2. I > would strongly prefer the latter, and this would affect my vote: I > don't want two messaging systems in Django, and if user messages are > not deprecated, then we do have two systems.
I agree that using deprecated code in the core is setting a bad example. A quick review of the code shows 8 calls to message_set.create: 3 in auth, 2 in admin, and 3 in the create/update/delete family of generic views. This definitely sounds to me like a manageable update for 1.2. Per feedback from Jacob, Chris, and Luke, I updated the notes on the existing API, the transition plan, and the potential API on the wiki: http://code.djangoproject.com/wiki/SessionMessages Cheers, Tobias -- Tobias McNulty Caktus Consulting Group, LLC P.O. Box 1454 Carrboro, NC 27510 (919) 951-0052 http://www.caktusgroup.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. 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 -~----------~----~----~----~------~----~------~--~---
