I'm in support of fixing the problem, and this narrowly scoped
solution seems like a reasonable way to go about that.
-Paul
On Fri, Feb 10, 2012 at 11:45 AM, David Lowe wrote:
> Django devs -
>
> I would love to see my patch in
> https://code.djangoproject.com/ticket/17277 applied. It's a pretty
> small change, doesn't break backwards compatibility, and includes test
> coverage. It does introduce a new pattern which isn't used elsewhere
> in the django code (wrapping a broad exception class with a narrower
> subclass, to make it easier to catch).
>
> The ticket is currently in 'Design decision needed' (has been for
> several months). What's next?
>
> Thanks!
> David Lowe
>
> --
> 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.
>
--
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.