#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 Chris Jerdonek):
Hmm, I'm never thought of logging as "unreliable." But your point is a
good one. Using logging brings lots of advantages though: custom
formatting, central configuration, etc. I wonder if there is a way to make
Django logging more reliable. Is there one root cause?
Alternatively, I wonder if a helper function or logging tweak could be
used to allow toggling sending messages between Python's `logging` module
and straight `stderr`. Defaulting to the latter would address the
backwards compatibility point you cited (and "reliability") and support an
easier migration path.
--
Ticket URL: <https://code.djangoproject.com/ticket/29040#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.83892c857955b238a0aa359ce63cab96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
