-
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
Fail to add package where the latest release contains no installable wheel #4046
Comments
Can you try with poetry from master? We have a few improvements there for PEP440 version parsing. You can use pipx to install from master like so. pipx install --force --suffix=@master 'poetry @ git+https://github.com/python-poetry/poetry.git@master'
poetry@master --version |
Sorry, does not work yet.
|
I'm not really looking into this at all, just happened to notice that it's post1 in some places and post.1 in others. |
Hi, I'm having the same issue with poetry 1.1.11. The issue seems related to the fact that the package version (0.2.1.post1) has a post release separator (https://www.python.org/dev/peps/pep-0440/#post-release-separators) |
Just found out, that kaleido 0.2.1.post1 is a armv7l only release, there aren't even x86 artifacts for this release. I think poetry detects the latest version (0.2.1.post1) first and then tries to install this version. Then poetry recognizes that there's no installable candidate for the current architecture. This is definitely a bad practice from kaleido, however poetry should be able to find an installable candidate. |
I just digged into this issue, and found out that the 'Env' instance is not taken into account when resolving dependencies. That's why 0.2.1.post1 is choosen, although there's no installation candidate. I tried to pass the environment downto Maybe one of the core-devs can answer, why env is not accessible from anywhere, maybe even as a singleton? |
Having the same issue. Workaround I'm using is to add it as an exact requirement in my pyproject.toml:
|
that unconstrained that the latest version of kaleido has not published packages suitable for your system is a kaleido issue. this can be closed |
No, it's the job of the dependency resolution tool to get the latest available version which is compatible to the rest of my dependencies. |
... which is a duplicate of #707 |
This is overall not a bug; Poetry does not take wheel availability into account when solving. |
another workaroud is to add it as follows:
or fully open:
|
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
When I create a new project, I'm unable to add the package kaleido. (0.2.1.post currently)
I'm not sure if it's about the semver incompatible versioning (
0.2.1.post
) or if there's any other issue.Installing via pip works fine, however pip installs
0.2.1
(without .post)The text was updated successfully, but these errors were encountered: