It would make sense if management commands would automatically log
exceptions so they get processed as specified in the logging configuration
just like all other crashes.
Workarounds do exist, like adding a try/except to manage.py or writing a
decorator and apply it to all the management commands.
Ref #21429, which is about using logging for output in management
commands.
--
Ticket URL: <https://code.djangoproject.com/ticket/27877>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: johannes.linke@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:2>
* status: new => assigned
* owner: nobody => ChillarAnand
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:3>
* owner: ChillarAnand => (none)
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:4>
* owner: (none) => John Kang
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:5>
Comment (by karyon):
John do you still plan to work on this?
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:6>
Comment (by John Kang):
Replying to [comment:6 karyon]:
> John do you still plan to work on this?
Hi Karyon, I will be resuming work on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:7>
* owner: John Kang => (none)
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/27877#comment:8>