built-in management
commands, but I don’t think it is an appropriate way to execute custom
code on command error.
Cheers,
François Freitag
On 5/15/20 5:12 PM, Yo-Yo Ma wrote:
> Request exceptions have always been easy to manage, because you can use
> middleware, and there is the built-in
Hi Django Devs,
https://code.djangoproject.com/ticket/30245 suggests supporting Python
unittest `-k` option, to selectively run tests matching a keyword.
Currently, `-k` is the shorthand for `--keepdb` in Django.
A `--filter` flag was suggested to preserve backward compatibility.
Carlton suggeste
ficant savings can be
achieved using `.defer()` to reduce the size of the Python objects or
filtering/limiting the choices QuerySet. Another option is to use a
custom ModelChoiceIterator subclass to fetch the results using
`.iterator()`.
I would prefer Django to have consistent results by default, even
Hi Tom,
Thank you for the great summary.
> 2. Add support for the "watchdog" library as a replacement for
> pyinotify. Watchdog implements file system notifications for all major
> platforms using a fairly simple API, so we can remove polling and have
> instant reloading. Also support Watchman,
