Latest patch, including fail_silently, is up for review: http://code.djangoproject.com/attachment/ticket/4604/django-contrib-messages-e4da706e1152.diff
Cheers, Tobias 2009/12/3 Tobias McNulty <tob...@caktusgroup.com> > The simplest solution is to catch the exception in the generic views. >> Another option is to add a 'fail_silently' keyword argument, >> defaulting to False, like the mail sending API. It would need to be >> added to all the shortcut functions, and used in the generic views and >> anywhere that you cannot rely on there being a current authenticated >> User. Docs should include something about it being intended for re- >> usable apps. >> > > Good catch. fail_silently sounds good to me. I'll add. > -- 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-develop...@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.
