#24398: Built in webserver not reloading Python files upon requests
----------------------------------+--------------------------------------
Reporter: hyperknot | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Resolution:
Keywords: server runserver | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by carljm):
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* needs_docs: 1 => 0
Comment:
We usually don't set any of those flags unless the ticket has a patch to
begin with.
I'm afraid the only way this ticket is likely to be solved is if someone
who can reproduce it tracks down the root cause - and right now the known
set of people who can reproduce it includes only yourself :/ Clearly
runserver is not behaving correctly on your system, but at this point it's
impossible to say whether it's a bug in runserver or something else about
your system.
You could experiment with the `--noreload` and `--nothreading` options to
see how they change the behavior. (Obviously with `--noreload` it's
expected for the server to never auto-reload on changes to `.py` files,
but it might be interesting to know if this changes the shutdown issue
you're seeing.)
--
Ticket URL: <https://code.djangoproject.com/ticket/24398#comment:10>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.e13089182d9bc3cc13fd953edb9bb5f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
