On Tue, Nov 3, 2009 at 12:27 PM, Waylan Limberg <way...@gmail.com> wrote: > I couldn't help but notice the docs suggest setting MESSAGE_STORAGE like so: > > MESSAGE_STORAGE = 'cookie.CookieStorage' > > Just yesterday, in reference to another upcoming feature, Jacob > commented that he would prefer all such settings to require full paths > only. In other words you would remove the attempt to import from a > default location first. So the correct setting would be: > > MESSAGE_STORAGE = 'django.contrib.messages.storage.cookie.CookieStorage' > > Obviously, it's not my place to say for sure, but I got the impression > this should apply to all new features.
Yes, please. Special-casing built-in backends requires more code and leads to the impression that external backends are somehow second-class citizens This isn't -- or shouldn't be -- true. Jacob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
