#31543: Default output buffering on in tests
-------------------------------------------------+------------------------
Reporter: Adam (Chainz) Johnson | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
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 |
-------------------------------------------------+------------------------
Following #31370, the `--buffer` option is supported for both parallel and
non-parallel tests.
I think we should default to turning it *on* for all users, and provide a
`--no-buffer` option to disable this behaviour.
This will improve output for many users, and increase speed for those
projects whose tests currently print a lot of output. It has the risk of
breaking some workflows of extracting information from tests ˙using
`print()`, but since the output is only hidden for passing tests, I think
this should be fairly niche.
--
Ticket URL: <https://code.djangoproject.com/ticket/31543>
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/053.3b74f04d85def8f484577743757449c3%40djangoproject.com.
