On Feb 19, 12:49 am, Malcolm Tredinnick <[email protected]> wrote: > On Wed, 2009-02-18 at 04:28 -0800, mrts wrote: > > The old Field.default_error_messages dict and corresponding > > logic is no longer required (and removed in my branch) as default > > error messages live in core/validators now. > > It *is* still required. Firstly, it's a very useful way of specifying > holistic error messages. Secondly, removing it would be backwards > incompatible in a major way (many custom fields would no longer work > properly, for example).
Agreed. > When I get out from under some work stuff this week, I'm going to commit > what I've been merging (it a merge of yours and Honza's git branches and > a lot of editing and review changes) into a subversion branch so that > more people can test it. I'm then happy to pull in and review changes > from git branches if you guys want to work on it there, but we need to > have this done in a more general way. We've all dropped the ball a bit > -- I thought the problems that were creeping in were going to simple to > fix up in review; I was wrong. It's the broken-windows problem, where > one little variation from "great" leads to another and another, without > realising it. Sounds good. Keep us updated and let know if you need us to work on something. Best, Mart --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
