You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pytest for example is getting installed as version 6.2.5 even though the latest is 8.3.5.
I'm not quite sure why this is happening, but I'm able to recreate the behavior on my local machine, with both pip and uv.
At first I thought it was due to a dependency conflict, but pinning pytest==8.3.5 results in a successful resolution, and the correct (newer) pytest version is installed. So there is no package forcing an older pytest. Using the --no-cache flag with uv doesn't seem to change the behavior either.
I suppose we could just set lower bounds on some of the dependencies. But I'd like to understand why this is happening.
The text was updated successfully, but these errors were encountered:
It looks like something is causing the resolver to choose ipython==8.12.3, which requires pytest<7.
Why? I have no idea, but changing ipython[all] to ipython in the requirements file results in the latest pytest being installed (although ipython==8.12.3 is still installed despite not being the latest)... so apparently one of the extra dependencies specified by all is leading the resolver down a bad path...
Possibly the pytest-asyncio<0.22 pin? Since it's the only extra dependency with an upper bound on that list.
one clue -- ipython==8.13.2 is the last version of ipython which supports Python 3.8, and I'm testing in a Python 3.8 env so that does explain why older ipython versions are being used...
Recent CI runs are installing old versions of many packages, despite no version pins:
Click to expand
pytest
for example is getting installed as version 6.2.5 even though the latest is 8.3.5.I'm not quite sure why this is happening, but I'm able to recreate the behavior on my local machine, with both
pip
anduv
.At first I thought it was due to a dependency conflict, but pinning
pytest==8.3.5
results in a successful resolution, and the correct (newer)pytest
version is installed. So there is no package forcing an olderpytest
. Using the--no-cache
flag withuv
doesn't seem to change the behavior either.I suppose we could just set lower bounds on some of the dependencies. But I'd like to understand why this is happening.
The text was updated successfully, but these errors were encountered: