#29026: Make makemigrations scriptable / script-friendly
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
makemigrations,scripting,stderr,stdout| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
My original use case was a non-interactive one (inside a container). But
again, you raise a good point. Obviously, piping to `stdout` won't work if
interactivity is required (because you'd want user prompts to go to
`stdout`). This is true of any script, not just Django management
commands. Other than that, I don't think the changes I've described would
''hurt'' things in that case, aside from possibly the "reliability" issue
you mentioned [https://code.djangoproject.com/ticket/29040#comment:3
here]. That though could be addressed by my
[https://code.djangoproject.com/ticket/29040#comment:4 follow-up comment]
to yours. If we wanted a fancier solution, the "structured" `stdout` could
be outputted only in non-interactive mode.
--
Ticket URL: <https://code.djangoproject.com/ticket/29026#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.e89350eef731c0a0b1b643ce06dac57e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
