Nick Coghlan ncoghlan at gmail.com
Thu Nov 9 20:58:45 EST 2017

• Previous message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
• Next message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 10 November 2017 at 11:53, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 10 November 2017 at 11:32, Nathaniel Smith <njs at pobox.com> 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

Issue filed for pytest here: https://github.com/pytest-dev/pytest/issues/2908

I haven't checked nose2's behaviour.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
• Next message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list