#9455: Undefined local `error` in the LaxOptionParser._process_args method
-------------------------------------+--------------------------------------
Reporter: egenix_viktor | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords: LaxOptionParser
_process_args undefined local error
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by egenix_viktor):
It seems to me, that the application works, actually. It seems to handle
the NameError exception, then starts as expected. So this problem turns
into a new question:
* Why does Django use such an exception for its normal execution flow?
It seems to be a design flaw for me. Or I might not aware of something
important about Django...
Thanks for your comments in advance.
--
Ticket URL: <http://code.djangoproject.com/ticket/9455#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
