#11957: runserver must be restarted after error in admin.py
------------------------------------------------+---------------------------
Reporter: carljm | Owner: nobody
Status: closed | Milestone:
Component: django-admin.py runserver | Version: 1.1
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------+---------------------------
Comment (by kmtracey):
Rather than re-opening this, it might be more useful to start a discussion
on the developers list about the problem. Comments in #8245 show that the
approach that was checked in was taken after IRC discussion involving at
least two committers. For some reason the alternate approach was
rejected, and I don't know why that was. I agree that only-pop-up-once-
and-then-go-away-until-server-restart exceptions are bad, and it might be
worth revisiting. But the ticket tracker is probably not the right place
for the discussion (the query on rationale in #8245 went unanswered).
--
Ticket URL: <http://code.djangoproject.com/ticket/11957#comment:4>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
