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
It seems like the behavior reported in #3675 has resurfaced after the 0.2.35 release.
I can see the code introduced as a fix has been removed in a major refactor of the marker trees here.
root@8bc75a13208d:/# python -V Python 3.11.9 root@8bc75a13208d:/# uv -V uv 0.2.36 root@8bc75a13208d:/# pip -V pip 24.0 from /usr/local/lib/python3.11/site-packages/pip (python 3.11) root@8bc75a13208d:/# pip install --dry-run pickleshare Collecting pickleshare Using cached pickleshare-0.7.5-py2.py3-none-any.whl.metadata (1.5 kB) Using cached pickleshare-0.7.5-py2.py3-none-any.whl (6.9 kB) Would install pickleshare-0.7.5 [notice] A new release of pip is available: 24.0 -> 24.2 [notice] To update, run: pip install --upgrade pip root@8bc75a13208d:/# uv pip install --dry-run --system pickleshare Resolved 3 packages in 18ms Would download 3 packages Would install 3 packages + pathlib2==2.3.7.post1 + pickleshare==0.7.5 + six==1.16.0 root@8bc75a13208d:/#
The text was updated successfully, but these errors were encountered:
Thanks for the report!
Sorry, something went wrong.
I believe this is now fixed (in v0.3.0).
No branches or pull requests
It seems like the behavior reported in #3675 has resurfaced after the 0.2.35 release.
I can see the code introduced as a fix has been removed in a major refactor of the marker trees here.
The text was updated successfully, but these errors were encountered: