The code you removed was trying to catch an error created by using illegal options or arguments in one of the commands. Apparently optparse still prints the usage message, but you also see the Python error.
It looks like sys.exit(3) is raising an exception that no one has ever noticed before. Not sure if it's worth it, but maybe specifying a more specific kind of exception would solve the problem. Todd On Mon, 2007-09-10 at 23:38 -0500, Adrian Holovaty wrote: > On 9/9/07, SmileyChris <[EMAIL PROTECTED]> wrote: > > It would seem this broke reloading of the built-in web server. > > I've fixed that in [6094]. > > Adrian > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
