On 10 November 2017 at 11:32, Nathaniel Smith <[email protected]> wrote: > Is this intended to be a description of the current state of affairs? > Because I've never encountered a test runner that does this... Which runners > are you thinking of?
Ah, you're right, pytest currently still requires individual developers to opt-in, rather than switching the defaults: https://docs.pytest.org/en/latest/warnings.html#pytest-mark-filterwarnings That's not the intention - we expect test runners to switch the defaults the same way unittest does: https://docs.python.org/3/library/unittest.html#unittest.TextTestRunner So that's likely part of the problem. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia _______________________________________________ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com