-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
pytest uses deprecated convert
argument in attr's attrib
#3280
Comments
thanks for the note, this has been fixed in #3228 and will be released in the next feature release |
Thanks @RonnyPfannschmidt! |
@RonnyPfannschmidt - any idea when the next feature release will be? If it's a long way off, I have a four-line shim that would fix this without a dependency bump. |
seeing this issue pop-up now on |
Update your pytest then! |
Workaround for pytest-dev/pytest#3280
Works perfectly on python==3.6.8 and pytest==5.2.0. Update the pytest version to solve the problem. |
thanks @geraldoandradee @Zac-HD doing the upgrade anyhow, |
- Pytest reference [0] - amqp reference [1] [0] pytest-dev/pytest#3280 [1] celery/kombu@b51d1d6 Change-Id: I676f54abf27e27646ae9ded4f1c2648824b047c9
I was surprised, dude, believe me. This is the first time I ever saw this. But since this issue first happened in 2018, it seems to be an old issue. Kind of a bummer. |
@rohansb It looks to me like |
@leon-barrett I just ran into this same issue and pinning |
This is done because we now use Node.get_closes_marker, which is introduced in pytest 4.1. However, we can't use 4.1 or 4.2 since those don't play well with attrs==19.2.0. See also pytest-dev/pytest#3280
Because idk why using pytest 4.1.1 suddenly yields an error like here: pytest-dev/pytest#3280.
I checked this with pytest 3.4.1 and master (3.4.2.dev42+ge980fbbe):
(That second bit of
PYTHONWARNINGS
is to avoid #1403.)This is in a fresh virtualenv after
pip install pytest
:For context on why I care: I contribute to another project that's turning on "deprecation warnings as errors" in our CI. It's not so hard for us to special-case ignore this warning, but I thought I should mention it here.
The text was updated successfully, but these errors were encountered: