#29470: Add output to makemigrations and migrate commands with --noinput
---------------------------------------+------------------------
               Reporter:  kurtwheeler  |          Owner:  nobody
                   Type:  New feature  |         Status:  new
              Component:  Migrations   |        Version:  1.11
               Severity:  Normal       |       Keywords:
           Triage Stage:  Unreviewed   |      Has patch:  0
    Needs documentation:  0            |    Needs tests:  0
Patch needs improvement:  0            |  Easy pickings:  0
                  UI/UX:  0            |
---------------------------------------+------------------------
 The `--noinput` option to makemigrations seems to also mean "no output".
 It would be nice for scripting purposes if there could be some kind of
 output. When writing a script that helps manage migrations, it would be
 nice to be able to detect that the migrations needed input from the
 developer so that the script can fail gracefully and inform the developer
 that manual intervention is required. Right now the options seem to be to
 not use the `--noinput` options and have the prompt interrupt the script,
 or to use the option and have no idea when migrations failed because they
 required input.

 I'm not very picky as far as how this functionality should be implemented
 goes. I would think that a little warning like
 "No migrations run because input was required but --noinput option was
 specified."
 would be sufficient. This could be output to stdout or stderr, either all
 the time or perhaps only if an additional option was set.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29470>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.d9fec91190999a4d646d2205054a812f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to