-
Notifications
You must be signed in to change notification settings - Fork 2.2k
env: Add surrogate for pytest.deprecated_call for ptyest<3.9 #2923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@YannickJadoul or @rwgk Any chance y'all have time for a quick stamp? |
I'd also be fine with telling pybind11 to fail fast if an old version of Lemme know! |
I just looked, pytest 3.9 was released in October 2018, nearly 2.5 years ago. |
Er, only caveat is that Ubuntu 18.04 also provisions pytest==3.3.2 for CPython 3.6.9 :(
In that case, it'd be requisite that testing be done inside a We OK making that constraint? (and do we do that in CI?) |
Reviewing CI, seems like yeah, EDIT: Er, easy to do in Python code, less trivial in tracing back through CMake logic. Will need to revisit tomorrow or next week :( |
I like this solution; unlike a normal Python package, we are not able to require Python things; so being able to use pytest in the default environment for reasonably recent OS's (Ubuntu 18.04) is nice. |
I think we used to use the default pytest, and this got changed in the CI to force a newer pytest. As long as it's clearly marked to be removed when we do bump the minimum pytest, I think it's fine. This is useful for deploying pybind11 in package managers, where they generally use the system packages for dependencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In support of Henry's approval.
Gotcha, thank ya for the rationale and and history - and happy to merge in with less work haha. |
Description
Resolves #2922
Suggested changelog entry:
Testing only; doesn't merit a change?