#29040: test database creation log output doesn't use consistent stream -------------------------------------+------------------------------------- Reporter: Chris Jerdonek | Owner: nobody Type: | Status: new Cleanup/optimization | Component: Testing framework | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted stdout,stderr,database,creation | Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham): I guess that would have the similar [https://docs.djangoproject.com/en/dev/releases/1.10/#runserver-output- goes-through-logging backwards compatibility issues] as when we changed runserver to use logging, yes? I don't know, I've always thought of print/stdout/stderr.write as simpler and "more reliable" than logging. -- Ticket URL: <https://code.djangoproject.com/ticket/29040#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 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/067.25ee23b1af4ea6069008d56012ec7d80%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.