-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Release with build number is not included as installation option in lock file #5543
Comments
Probably, a caching issue. Try clearing your cache (at least for |
Ah, cool. Some other members on my team must've had only the newer versions, and we found that if I ran |
Trying to solve for inconsistencies like that might be more effort than worth it. Happy to review PRs if folks have ideas how best to tackle this without introducing new issues. Poetry does rely on the Cache-Control header to manage HTTP cache at present. So, this could have just been a timing issue. As an interim mitigation, folks can use Closing for now. But as mentioned above, happy to review PR for improving status quo. |
Makes sense, and no worries about the difficulties solving this. Unfortunately we cannot do |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
The
pytest-asyncio
project has two wheels for 0.18.3: https://pypi.org/project/pytest-asyncio/0.18.3/#filespytest_asyncio-0.18.3-py3-none-any.whl
pytest_asyncio-0.18.3-1-py3-none-any.whl
Note the extra build tag
-1
in the second one (https://packaging.python.org/en/latest/specifications/binary-distribution-format/#file-name-convention). The second one was released because the first was missing a file (pytest-dev/pytest-asyncio#314).It seems poetry is ignoring the second one: with a requirement like
pytest-asyncio = "0.18.3"
, poetry generates a lock file that contains only the sdist and the first wheel:This is forcing us to pin to this dev to 0.18.2, because we need the missing file.
(Thanks for poetry!)
The text was updated successfully, but these errors were encountered: