On 5/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> That was exactly why I didn't change clean_data (my initial "fix" was
> just to name it cleaned_data). It's already used in lots of code, so the
> impact of change it is larger. Changing the undocumented feature is less
> disruptive. Unnecessarily intrusive backwards-incompat changes seem
> mean.
For me, an AttributeError from clean_data is a much more friendly
change than silently ignoring code like:
def clean_email(self):
"""Prevent account hijacking by disallowing duplicate emails."""
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
