#29470: Add output to makemigrations and migrate commands with --noinput
------------------------------+--------------------------------------
Reporter: Kurt Wheeler | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Jacob Walls):
* status: closed => new
* has_patch: 0 => 1
* resolution: duplicate =>
Comment:
Like Chris, I believe this should be handled separately. Whereas the idea
in #29026 is to move some of `makemigrations`'s current output from
`stdout` to `stderr`, the error messaging asked for in this ticket should
go to `stderr` regardless, so they don't depend on the changes in #29026.
[https://github.com/django/django/pull/14805 PR to ~~implement this part
of Chris's comment:]
> In addition, if the answers to one or more questions (provided either
automatically from --no-input or manually by the user) cause no migrations
to be applied, then the migration command class could log that in any case
so the user knows.
I'm in favor of starting with just that change, and only for the non-
interactive questioner, i.e. `--noinput`.
--
Ticket URL: <https://code.djangoproject.com/ticket/29470#comment:3>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.5b486f6f7d12229e7a0757a32c4bec4a%40djangoproject.com.
