* needs_better_patch: 1 => 0
* ui_ux: => 0
* easy: => 0
Comment:
I worked on a refactor of commands output using logging infrastructure,
adding new !BaseCommand.info() and !BaseCommand.error() proxy methods, and
deprecating self.stderr and self.stdout. Hopefully this is in the right
direction, as of jezdez comment:5.
--
Ticket URL: <https://code.djangoproject.com/ticket/15107#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by claudep):
Just a note to any potential reviewer: as this patch is quite extensive, I
will keep a local branch updated with current trunk. However, I will not
spam this ticket each time I rebase my branch. So just ping me if/when you
are interested to review it (hopefully during the 1.5 timeframe!)
--
Ticket URL: <https://code.djangoproject.com/ticket/15107#comment:9>
Comment (by Mike <leachim@…>):
@claudep
If BaseCommand has .info() and .error(), it might be nice to be complete
and include .debug(), .warning() and .critical(), that also get output to
the stdout/stderr passed to the command.
Then the verbosity argument could potentially be updated to also take
strings, so you could for example do -v W to only have output at warning
level or higher.
--
Ticket URL: <https://code.djangoproject.com/ticket/15107#comment:10>
* needs_better_patch: 0 => 1
Comment:
Thanks Mike, that's an interesting comment. I'd like to push patch for
#18325 first, then rewrite this one with your idea in mind.
--
Ticket URL: <https://code.djangoproject.com/ticket/15107#comment:11>
* status: new => closed
* resolution: => fixed
Comment:
Let's close this one in favour of #21429
--
Ticket URL: <https://code.djangoproject.com/ticket/15107#comment:12>