You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As detailed at #4744 (comment), no_deprecated_call (an old MDA testing utility) now requires an explicit warning class specification to work--so it'll choke with warnings.warn("boo"), but succeed with warnings.warn("boo", UserWarning).
Should probably be fixed (and or/upstreamed to pytest or put in some pytest plugin perhaps).
It is still actively used in our suite, but only a little bit, and perhaps not enough to have tracked the increased complexity of the warnings system from Python 2->3.
The text was updated successfully, but these errors were encountered:
Good point on trade-offs here -- IMO since it is actively used in our test suite (and would love to use it in the scenario of #4744, although it probably will have to happen after 2.8.0), we should maintain it. Between the last change 7 years ago the only difference seems to be that the default behaviour seems to have changed, so IMO the maintennace cost isn't extreme. I opened #4747 to fix it.
As detailed at #4744 (comment),
no_deprecated_call
(an old MDA testing utility) now requires an explicit warning class specification to work--so it'll choke withwarnings.warn("boo")
, but succeed withwarnings.warn("boo", UserWarning)
.Should probably be fixed (and or/upstreamed to
pytest
or put in somepytest
plugin perhaps).It is still actively used in our suite, but only a little bit, and perhaps not enough to have tracked the increased complexity of the warnings system from Python 2->3.
The text was updated successfully, but these errors were encountered: