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
{{ message }}
Repository navigation
Poetry doesn't install the correct dependency according to its supported Python version #5447
In this case, poetry attempts to install only the first URL--if I look at poetry.lock, I see something like
[[package]]
name = "package"
version = "1.2.3"
description = ""
category = "main"
optional = false
python-versions = "*"
[package.source]
type = "url"
url = "https://some.url.com/path/to/package-cp37-cp37-linux_x86_64.whl"
So, poetry only stores a single URL in the lock file, despite there being multiple URLs specified in pyproject.toml
EDIT: The python versions above were incorrect (i.e., previously, it had "~3.7", but it should have been "~3.7.0"). I've fixed it now. Unfortunately, that doesn't fix the behavior.
@roipoussiere it looks as though you have now published ocp-vtk to pypi, so you should be able simply to go: ocp-vtk = "^7.5.3" - right?
Not to say that this isn't a valid bug report - possibly poetry should do a better job with the list of urls and markers that you were using. But I expect that the main line case should work just fine with different python versions and platforms and so on.
(by the way the pyproject.toml that you linked to is broken, it has a whole series of dead urls because you have ocpvtk where you want ocp_vtk)
it looks as though you have now published ocp-vtk to pypi, so you should be able simply to go: ocp-vtk = "^7.5.3" - right?
Yes, I don't need to specify wheel urls now.
by the way the pyproject.toml that you linked to is broken, it has a whole series of dead urls because you have ocpvtk where you want ocp_vtk
fixed, thanks.
Not to say that this isn't a valid bug report
I don't understand why this isn't a valid bug report. Poetry downloads the wrong wheel according to my python version, this is not an expected behavior, so I made a bug report.
Since the dependency is published on PyPI I don't personally need a response now, so feel free to close this if you think is not relevant.
Activity
kmsquire commentedon Apr 14, 2022
I see a similar problem with something like the following:
In this case, poetry attempts to install only the first URL--if I look at
poetry.lock, I see something likeSo, poetry only stores a single URL in the lock file, despite there being multiple URLs specified in
pyproject.tomlEDIT: The python versions above were incorrect (i.e., previously, it had
"~3.7", but it should have been"~3.7.0"). I've fixed it now. Unfortunately, that doesn't fix the behavior.lypwig commentedon Apr 15, 2022
If I use the
{ platform = "linux", python = "~3.8", url = ...}approach, Poetry doesn't even try to download the wheel. 🤔dimbleby commentedon Apr 16, 2022
@roipoussiere it looks as though you have now published ocp-vtk to pypi, so you should be able simply to go:
ocp-vtk = "^7.5.3"- right?Not to say that this isn't a valid bug report - possibly poetry should do a better job with the list of urls and markers that you were using. But I expect that the main line case should work just fine with different python versions and platforms and so on.
(by the way the
pyproject.tomlthat you linked to is broken, it has a whole series of dead urls because you haveocpvtkwhere you wantocp_vtk)lypwig commentedon Apr 17, 2022
Yes, I don't need to specify wheel urls now.
fixed, thanks.
I don't understand why this isn't a valid bug report. Poetry downloads the wrong wheel according to my python version, this is not an expected behavior, so I made a bug report.
Since the dependency is published on PyPI I don't personally need a response now, so feel free to close this if you think is not relevant.
dimbleby commentedon Apr 17, 2022
Apologies if my double-negative confused you. We are agreeing.
github-actions commentedon Mar 1, 2024
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.