On Tue, Oct 13, 2009 at 3:27 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > as an alias. Note that this is a reversal of argument order from the > proposed API. I'm not absolutely tied to this suggestion - I'm just > noting that adding Django support for Python logging is also on the > cards for v1.2, and it seems weird that we would introduce two APIs > with similar external APIs, but not try to maintain parity.
I updated the API on the wiki. The levels/classes will likely be different, because logging and messaging are two very different things, but keeping the argument order the same is probably a good thing. > 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? > Lastly, one issue that seems unaddressed is the transition plan for > replacing user.message_set. The preamble to the wiki page makes a > compelling argument for ditching message_set, but remains silent on a > proposal for how Django (as a project) should be treating this new > alternative. > > The solution might well be "use it if you want, ignore it if you > don't", but given the problems with user.message_set, it might be > worth giving some thought to a deprecation/transition plan. 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 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? 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 -~----------~----~----~----~------~----~------~--~---
