I don't know. Can you propose a patch so we can see what's involved? How
would a "production" web server (nginx, apache, etc.) handle the issue?
I'm more interested in moving runserver toward using gunicorn [0] (Windows
support seems the main blocker to proceeding there) than adding more
featur
Sometimes it's not started because some modern orchestration tools such as
ansible-container and docker-compose (perhaps more) start everything at
once, and django might be faster than the db, or I have to fix something
with the db orchestration tool.
I noted we might have the same issue with redi
Could you explain the use case a bit more? Why is your database failing on
a regular basis?
On Wednesday, March 1, 2017 at 4:00:12 PM UTC-5, James Pic wrote:
>
> Hi all,
>
> It seems like runserver won't retry to connect to the database after a
> failing connection. Once the db server is up, it
Hi all,
It seems like runserver won't retry to connect to the database after a
failing connection. Once the db server is up, it looks like I have to
restart runserver manually.
If this is correct, may I suggest that we make runserver retry connecting
to the database if it fails ?
Thanks
--
You
On 01/03/17 01:53, Tim Martin wrote:
On Tuesday, 28 February 2017 13:39:21 UTC, Luke Plant wrote:
On 28/02/17 15:24, Marten Kenbeek wrote:
What about adding a filter |definedthat returns True if a
variable is defined, False otherwise? It may not solve any
problems when it's
In the context of template variable interpolation i.e. `{{ }}`
syntax, it is defined that `x` in this case will get converted to
the empty string (or your 'string_if_invalid' setting) -
https://docs.djangoproject.com/en/dev/ref/templates/api/#how-invalid-variables-are-handled
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2017/mar/01/bugfix-release/
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop
