Support multiple private repositories about poetry HOT 7 CLOSED

@languitar

[[tool.poetry.source]]
name = "foo"
url = "https://foo.bar/simple/"

[[tool.poetry.source]]
name = "bar"
url = "https://bar.baz/simple/"

This is equivalent to

tool.poetry.source = [
 { name = "foo", url = "https://foo.bar/simple/" },
 { name = "bar", url = "https://bar.baz/simple/" }
]

from poetry.

This is already supported.

You can actually add any number of repositories as described here: https://poetry.eustace.io/docs/repositories/#install-dependencies-from-a-private-repository

When you install packages, poetry will look sequentially in every repository configured.

from poetry.

How would that work with the repository specification inside the pyproject.toml in tool.poetry.source?

from poetry.

Oh yes thanks. I missed the double brackets when reading the examples

from poetry.

Can someone confirm what the resolution order is for looking up packages when there are multiple sources defined? Based on my ad-hoc testing it would appear as though every source repo is used for every package lookup, which seems odd. I would have expected the resolver to stop at the first source that provided a valid match.

from poetry.

[[tool.poetry.source]]
name = "foo"
url = "https://foo.bar/simple/"

[[tool.poetry.source]]
name = "bar"
url = "https://bar.baz/simple/"

This is equivalent to

tool.poetry.source = [
 { name = "foo", url = "https://foo.bar/simple/" },
 { name = "bar", url = "https://bar.baz/simple/" }
]

Just a heads-up for anybody coming across this, wondering why it won't work for them.

Using an array of tables seems to be broken for source:

poetry check
Error: [urls.tool] {'poetry': {'source': [{'name': 'foo', 'url': 'https://foo.bar/simple/'}, {'name': 'bar', 'url': 'https://bar.baz/simple/'}]}} is not of type 'string'

from poetry.

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.

from poetry.