Closed AetherUnbound closed 6 years ago
I'll look into why the build is failing.
Thanks for the PR. Looks like failures are for python versions greater than 3.5, which are only using pytest 3.3 for some reason. I'd suggest updating the pytest version in setup.py
to >=3.6.0
and try again.
Thanks @Lemmons! I hate to hurt compatibility, are you comfortable with me bumping the pytest requirement? Alternatively, I could do a check to see if item
has the get_closest_marker
method and prefer that over get_marker
. That would allow pytest-raises
to still be compatible with pytest<3.5
.
That is fine with me. I usually feel like we should be using the latest test tools possible, but I also understand that that often isn't the case.
I tend to agree, but I don't mind adding backwards compatibility here :)
Thanks again. This has been released as pytest-raises 0.9
No way! Thanks for the super quick response!
I recently got the following deprecation warning when using
pytest-raises
with the latestpytest
:Pytest version:
Pytest has a guide for upgrading markers, which is what I followed: https://docs.pytest.org/en/latest/mark.html#updating-code
All unit tests passed on my local machine, let me know if there's anything else I need to add!