Closed davidism closed 3 years ago
Looks like https://github.com/pytest-dev/py/issues/273 and https://github.com/pytest-dev/pytest/issues/9181 are the tracking issues, this is already fixed in the next release according to that.
@davidism the release is already available
Yes, I just realized it was released literally right after I did my monthly requirements pin updates. Thanks!
the release is already available
(and https://github.com/pytest-dev/py/issues/273)
Where? Idk, I basically have no idea what I am doing, but couldn't find anything in this repo nor in the py
repo, nor is there anything new on pypi. All my dependencies are up-to-date.
What do I have to do?
I get the exact same error.
the release is already available
what release version of what package or python fixes this problem?
i'm asking, because i also get the exact same error with python 3.11.2 and pytest 7.2.1.
i've also tried including apipkg==3.0.1 in my requirements.txt and it made no difference
Open a new issue with a minimal reproducible example if you're having a problem. Commenting "this still happens" with no additional details on a two year old closed issue isn't helpful.
Upgrading library py
to 1.11.0
solved the problem for me.
i also get the exact same error with python 3.11.2 and pytest 7.2.1.
You may have an older version of py
left behind in your python environment (because pytest used to depend on it) see this comment for more details https://github.com/pytest-dev/pytest/issues/9181#issuecomment-1513234948
I wanted to run Jinja's tests against 3.11.0a1. However, I get the following exception from apipkg when pytest is run from tox. If I create a 3.11 virtualenv manually and run pytest directly, it succeeds.