"Karen Tracey" <[EMAIL PROTECTED]> writes: > "Karen Tracey" <[EMAIL PROTECTED]> > writes: > > The fix for #2348 changes the error from "Unbound local error" to "Type > error: cannot > resolve > > keyword [whatever] into field". > > Illustrating just why the current syntax is hard to give good error > messages for ;-) > > Well it is a big improvement in that it points you to exactly where it runs > into trouble, > whereas the unbound local error was a confusing red herring.
Yes, it's better. But "cannot resolve keyword [whatever] into field" is also a red herring when the misspelled bit was never intended to be a field name in the first place. Pity the poor user when the converse happens and "gate" is misspelled as "gte"! > (I have no energy at the moment to consider the pros and cons of > changing the syntax here; I was just trying to save anyone the > trouble of opening a ticket for something that had just been fixed.) Thanks; I didn't mean to seem ungrateful for the report. I just have bigger fish to fry. ;-) -- Dave Abrahams Boost Consulting www.boost-consulting.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
