#22857: Django 1.7 runserver auto-reload : setting behaviour by extensions
-------------------------------------+-------------------------------------
Reporter: artscoop | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version:
commands) | 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by artscoop):
@claudep I didn't know it was possible to reset/reload translations
separately (even though it makes perfect sense), but I think it's better
than the --noreload-translations, because the command option would have to
be officially documented, and maybe deprecated very quickly.
The suggestion about AJAXing a view until the server comes back is good
but a bit hacky.
I do think resetting translation cache on .mo change is the best idea, and
would be more immediate than reloading the whole dev server (which ideally
should be reloaded on code changes only). It seems that resetting the
translation is a simple as in this example:
https://djangosnippets.org/snippets/1704/
--
Ticket URL: <https://code.djangoproject.com/ticket/22857#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.864c382c09dadc58b90f0e606d2653c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
