On Wed, Oct 14, 2009 at 7:45 AM, Tobias McNulty <tob...@caktusgroup.com> wrote: > > On Tue, Oct 13, 2009 at 3:27 AM, Russell Keith-Magee > <freakboy3...@gmail.com> wrote: >> Secondly, I share Chris' concern about overloading 'messages'. This >> overlaps with the bikeshed issue of what to call the new contrib >> package - whatever name is picked for the contrib package should >> probably be reflected in the context variable, etc. > > Okay, let's pick something other than 'messages' and stick to it. I'm > fine with "notifications", "notices", and maybe even "notes", but the > last one is a little ambiguous. Other ideas?
I'll stay out of this particular bikeshed, other than to note that Pinax ships with django-notifications, which has nothing to do with session-based messages. > I think the deprecation plan would look something like this: > > 1.2: user.message_set is officially deprecated but continues to work > unaffected > 1.3: user.message_set is still usable, but raises a deprecation > warning when it is used > 1.4: user.message_set is removed I was hoping for a little more detail than this - this is just Django's general deprecation plan, and I wouldn't expect that to change. What exactly do these steps mean in practice? What changes are going to be made to (for example) admin? Are there any other apps that will be affected? What will happen when I update from 1.2-1.3? 1.3-1.4? Is there a need for a transition API (e.g., a 'message_set' descriptor that actually sends messages to the new message backend)? > Are we comfortable ditching the auth Message model altogether (several > releases from now), or is someone actually using it for a legitimate > purpose that won't be supplanted by the proposed app? This is the sort of question we need to resolve for a deprecation plan. Do we just delete auth.Message? Do we migrate it to an contrib.old_messages app? I'm open to other suggestions. Personally, I don't have a problem deprecating auth.Message, if for no other reason than authentication has nothing to do with messaging. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
