#12456: Make `django.forms.util.ValidationError` and `django.core.exceptions.ValidationError` share ancestry ----------------------+----------------------------------------------------- Reporter: obeattie | Owner: nobody Status: new | Milestone: Component: Forms | Version: SVN Keywords: | Stage: Unreviewed Has_patch: 0 | ----------------------+----------------------------------------------------- There appears to be two (similarly named) `ValidationError`s in Django — one living in `django.core`, and a form-specific one living in `django.forms.util`. I can appreciate that they have slightly differing uses, but it does seem like they have a lot in common. So, there would be a few routes one could take here:-
1. Alias `django.forms.util.ValidationError` to the `django.core` one 2. Make the forms version a subclass of the `django.core` one 3. Make each share a common base exception Given how the exceptions are used, I'd say #2 would seem to make the most sense here, and wouldn't break anything. It's already rather confusing having two similarly-named exceptions, so I couldn't really see it being any more confusing to do this. -- Ticket URL: <http://code.djangoproject.com/ticket/12456> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-upda...@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
