"Karen Tracey" <[EMAIL PROTECTED]> writes: > On 2/9/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > However, you have obviously been bitten by a bad error message - I > would suggest that a good course of action would be to raise a ticket > with your specific example so that the error reporting of that part of > the query engine can be fixed up. > > 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 ;-) -- 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 [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 -~----------~----~----~----~------~----~------~--~---
