We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
after updating my pipenv, I noticed that pytest-redis (and also pytest-postgres) both raises on import due to:
ImportError: cannot import name 'TempdirFactory' from '_pytest.tmpdir'
the setup.cfg of pytest-redis doesn't have any version constraints, while pytest-postgresql's has >= 3.0.0.
>= 3.0.0
pytest changelog notes that importing TempdirFactory directly is now deprecated, and could become a hard error in 7.0.0: https://docs.pytest.org/en/stable/changelog.html#deprecations
The text was updated successfully, but these errors were encountered:
This issue can be temporarily fixed by downgrading pytest to the latest version before 7.0.0:
pytest==6.2.5
Now that pytest 7.0.0 is out, pytest-redis simply prevent pytest from starting.
Sorry, something went wrong.
the tmpdir_factory fixture with tmp_path_factory fixture.
The minimum supported pytest version should then be set to 6.2 ref: ClearcodeHQ/pytest-postgresql#533
Change typing imports, require pytest 6.2 minimum - closes #349
667e3e2
85fe76c
Merge pull request #361 from ClearcodeHQ/prepare-pytest-7
e40cba2
No branches or pull requests
after updating my pipenv, I noticed that pytest-redis (and also pytest-postgres) both raises on import due to:
ImportError: cannot import name 'TempdirFactory' from '_pytest.tmpdir'
the setup.cfg of pytest-redis doesn't have any version constraints, while pytest-postgresql's has
>= 3.0.0
.pytest changelog notes that importing TempdirFactory directly is now deprecated, and could become a hard error in 7.0.0: https://docs.pytest.org/en/stable/changelog.html#deprecations
The text was updated successfully, but these errors were encountered: