[SciPy-Dev] Need to filter DeprecationWarnings in the tests?

[Sebastian Berg]

Not sure how it is set up with pytest, but without pytest it was set
up, so that DeprecationWarning are raised during development testing
(so that upstream changes are loud) and printed in release versions.

I think that is not really a bad setup, so likely it is/would also be
used with pytest?

- Sebastian


On Fri, 2017-09-08 at 07:22 -0400, Warren Weckesser wrote:
> In the original version of a pull request that I am updating (https:/
> /github.com/scipy/scipy/pull/7190), I had filtered
> DeprecationWarnings in the unit tests.  Now that we are using pytest,
> is this still necessary?  According to https://docs.pytest.org/en/lat
> est/warnings.html, by default, pytest doesn't report
> DeprecatingWarnings, so it looks like there is no need to filter them
> with `numpy.tests.suppress_warnings()`.  Is that correct?
> 
> Warren
> 
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20170908/a5468f32/attachment.sig>