Malcolm Tredinnick said the following:
> The current latest patch fails in a dangerous way, which is why I'm
> against it. Fail safely (so that my data always gets saved when I call
> save()) and it's up for consideration.

Is the failure you mention just the __setattr__ issue, or is there
another issue you haven't mentioned? :)

If that is what you're referring to, I'll get to work on fixing it :)

-- 
Collin Grady

Man's reach must exceed his grasp, for why else the heavens?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to