Poetry 1.5 Source Priority (Error processing NoMethodError) #7431
Labels
T: bug 🐞
Something isn't working
Comments
DanielRejniak
changed the title
|
Seeing the same error on our end. We've set PyPI as a "primary" source per their documentation (with our private repo as "supplemental"), using command This creates an entry in [[tool.poetry.source]]
name = "PyPI"
priority = "primary"Is there an issue here due to the missing |
DanielRejniak
changed the title
DanielRejniak
changed the title
DanielRejniak
changed the title
1 task
|
We see the same error with: [tool.poetry.dependencies]
torch = { version = "2.0.1+cpu", source = "torchcpu" }
[[tool.poetry.source]]
name = "torchcpu"
url = "https://download.pytorch.org/whl/cpu"
priority = "explicit" |
torarvid
added a commit
to torarvid/dependabot-core
that referenced
this issue
Jun 30, 2023
Fixes dependabot#7431 When a github user has poetry >= 1.5.0, they will be nagged by a warning to run `poetry source add pypi`, which will add the following section to the users pyproject.toml: [[tool.poetry.source]] name = "PyPI" priority = "primary" This causes the problem outlined in dependabot#7431, that the index_finder will fail due to this section missing a `url`. This commit works around this issue by explicitly adding a url for the case where the source "name" is equal to "PyPI".
jurre
pushed a commit
to torarvid/dependabot-core
that referenced
this issue
Jul 3, 2023
Fixes dependabot#7431 When a github user has poetry >= 1.5.0, they will be nagged by a warning to run `poetry source add pypi`, which will add the following section to the users pyproject.toml: [[tool.poetry.source]] name = "PyPI" priority = "primary" This causes the problem outlined in dependabot#7431, that the index_finder will fail due to this section missing a `url`. This commit works around this issue by explicitly adding a url for the case where the source "name" is equal to "PyPI".
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Package ecosystem
Poetry
Package manager version
Language version
python 3.10
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
Context
Poetry 1.5.0 introduces priority key to sources. After the priority key was introduced all the dependencies failed to update with the following error.
Our
pyproject.tomlhas two sources one for pypi and one for out private repo.What is the error
All the packages fail to update the root of the error starts with
Error processing (NoMethodError)following with and attempt to strip the url in the updater. The example below is only one error for pyyaml package but all other packages yield the same error.What we expect
We would have expected the dependecies to be updated without the above errors.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
The easiest way to reproduce this error is to create a basic poetry project and add two sources one for pypi and one for private repo.
Next navigate to the Insights and observe the dependabot attempting to update the packages with the failure above.
The text was updated successfully, but these errors were encountered: