Repositories #

Poetry supports the use of PyPI and private repositories for discovery of packages as well as for publishing your projects.

By default, Poetry is configured to use the PyPI repository, for package installation and publishing.

So, when you add dependencies to your project, Poetry will assume they are available on PyPI.

This represents most cases and will likely be enough for most users.

Private Repository Example #

Installing from private package sources #

By default, Poetry discovers and installs packages from PyPI. But, you want to install a dependency to your project for a simple API repository? Let’s do it.

First, configure the package source as a secondary package source to your project.

poetry source add --secondary foo

Then, assuming the repository requires authentication, configure credentials for it.

poetry config <username> <password>
Depending on your system configuration, credentials might be saved in your command line history. Many shells do not save commands to history when they are prefixed by a space character. For more information, please refer to your shell’s documentation.

Once this is done, you can add dependencies to your project from this source.

poetry add --source foo private-package

Publishing to a private repository #

Great, now all that is left is to publish your package. Assuming you’d want to share it privately with your team, you can configure the Upload API endpoint for your publishable repository.

poetry config

If you need to use a different credential for your package source, then it is recommended to use a different name for your publishing repository.

poetry config
poetry config <username> <password>

Now, all the is left is to build and publish your project using the publish.

poetry publish --build --repository foo-pub

Package Sources #

By default, Poetry is configured to use the Python ecosystem’s canonical package index PyPI.

With the exception of the implicitly configured source for PyPI named pypi, package sources are local to a project and must be configured within the project’s pyproject.toml file. This is not the same configuration used when publishing a package.

Project Configuration #

These package sources may be managed using the source command for your project.

poetry source add foo
If your package source requires credentials or certificates, please refer to the relevant sections below.

This will generate the following configuration snippet in your pyproject.toml file.

name = "foo"
url = ""
default = false
secondary = false

Any package source not marked as secondary will take precedence over PyPI.


If you prefer to disable PyPI completely, you may choose to set one of your package sources to be the default.

If you prefer to specify a package source for a specific dependency, see Secondary Package Sources.

If you do not want any of the custom sources to take precedence over PyPI, you must declare all package sources to be secondary.

Default Package Source #

By default, Poetry configures PyPI as the default package source for your project. You can alter this behaviour and exclusively look up packages only from the configured package sources by adding a single source with default = true.

poetry source add --default foo
Configuring a custom package source as default, will effectively disable PyPI as a package source for your project.

Secondary Package Sources #

If package sources are configured as secondary, all it means is that these will be given a lower priority when selecting compatible package distribution that also exists in your default package source.

You can configure a package source as a secondary source with secondary = true in your package source configuration.

poetry source add --secondary foo

There can be more than one secondary package source.


All package sources (including secondary sources) will be searched during the package lookup process. These network requests will occur for all sources, regardless of if the package is found at one or more sources.

In order to limit the search for a specific package to a particular package repository, you can specify the source explicitly. This is strongly suggested for all private packages to avoid dependency confusion attacks.

poetry add --source internal-pypi httpx
httpx = { version = "^0.22", source = "internal-pypi" }

[[tool.poetry.source]] name = "internal-pypi" url = "" secondary = true

Supported Package Sources #

Python Package Index (PyPI) #

Poetry interacts with PyPI via its JSON API. This is used to retrieve a requested package’s versions, metadata, files, etc.

If the the package’s published metadata is invalid, Poetry will download the available bdist/sdist to inspect it locally to identify the relevant metadata.

If you want to explicitly select a package from PyPI you can use the --source option with the add command, like shown below.

poetry add --source pypi httpx@^0.22.0

This will generate the following configuration snippet in your pyproject.toml file.

httpx = {version = "^0.22.0", source = "pypi"}
If any source within a project is configured with default = true, The implicit pypi source will be disabled and not used for any packages.

Simple API Repository #

Poetry can fetch and install package dependencies from public or private custom repositories that implement the simple repository API as described in PEP 503.

When using sources that distributes large wheels without providing file checksum in file URLs, Poetry will download each candidate wheel at least once in order to generate the checksum. This can manifest as long dependency resolution times when adding packages from this source.

These package sources maybe configured via the following command in your project.

poetry source add testpypi
Note the trailing /simple/. This is important when configuring PEP 503 compliant package sources.

In addition to PEP 503, Poetry can also handle simple API repositories that implement PEP 658 (Introduced in 1.2.0). This is helpful in reducing dependency resolution time for packages from these sources as Poetry can avoid having to download each candidate distribution, in order to determine associated metadata.


Why does Poetry insist on downloading all candidate distributions for all platforms when metadata is not available?

The need for this stems from the fact that Poetry’s lock file is platform-agnostic. This means, in order to resolve dependencies for a project, Poetry needs metadata for all platform specific distributions. And when this metadata is not readily available, downloading the distribution and inspecting it locally is the only remaining option.

Introduced in 1.2.0

Some projects choose to release their binary distributions via a single page link source that partially follows the structure of a package page in PEP 503.

These package sources maybe configured via the following command in your project.

poetry source add jax
All caveats regarding slower resolution times described for simple API repositories do apply here as well.

Publishable Repositories #

Poetry treats repositories to which you publish packages as user specific and not project specific configuration unlike package sources. Poetry, today, only supports the Legacy Upload API when publishing your project.

These are configured using the config command, under the repositories key.

poetry config repositories.testpypi
Legacy Upload API URLs are typically different to the same one provided by the repository for the simple API. You’ll note that in the example of Test PyPI, both the host ( as well as the path (/legacy) are different to it’s simple API (

Configuring Credentials #

If you want to store your credentials for a specific repository, you can do so easily:

poetry config <username> <password>

If you do not specify the password you will be prompted to write it.


To publish to PyPI, you can set your credentials for the repository named pypi.

Note that it is recommended to use API tokens when uploading packages to PyPI. Once you have created a new token, you can tell Poetry to use it:

poetry config pypi-token.pypi my-token

If you still want to use your username and password, you can do so with the following call to config.

poetry config http-basic.pypi <username> <password>

You can also specify the username and password when using the publish command with the --username and --password options.

If a system keyring is available and supported, the password is stored to and retrieved from the keyring. In the above example, the credential will be stored using the name poetry-repository-pypi. If access to keyring fails or is unsupported, this will fall back to writing the password to the auth.toml file along with the username.

Keyring support is enabled using the keyring library. For more information on supported backends refer to the library documentation.


Poetry will fallback to Pip style use of keyring so that backends like Microsoft’s artifacts-keyring get a chance to retrieve valid credentials. It will need to be properly installed into Poetry’s virtualenv, preferably by installing a plugin.

If you are letting Poetry manage your virtual environments you will want a virtualenv seeder installed in Poetry’s virtualenv that installs the desired keyring backend during poetry install. To again use Azure DevOps as an example: azure-devops-artifacts-helpers provides such a seeder. This would of course best achieved by installing a Poetry plugin if it exists for you use case instead of doing it yourself.

Alternatively, you can use environment variables to provide the credentials:

export POETRY_PYPI_TOKEN_PYPI=my-token

See Using environment variables for more information on how to configure Poetry with environment variables.

If your password starts with a dash (e.g. randomly generated tokens in a CI environment), it will be parsed as a command line option instead of a password. You can prevent this by adding double dashes to prevent any following argument from being parsed as an option.

poetry config -- http-basic.pypi myUsername -myPasswordStartingWithDash

Certificates #

Custom certificate authority and mutual TLS authentication #

Poetry supports repositories that are secured by a custom certificate authority as well as those that require certificate-based client authentication. The following will configure the “foo” repository to validate the repository’s certificate using a custom certificate authority and use a client certificate (note that these config variables do not both need to be set):

poetry config /path/to/ca.pem
poetry config /path/to/client.pem

The value of certificates.<repository>.cert can be set to false if certificate verification is required to be skipped. This is useful for cases where a package source with self-signed certificates are used.

poetry config false
Disabling certificate verification is not recommended as it is does not conform to security best practices.

Caches #

Poetry employs multiple caches for package sources in order to improve user experience and avoid duplicate network requests.

The first level cache is a Cache-Control header based cache for almost all HTTP requests.

Further, every HTTP backed package source caches metadata associated with a package once it is fetched or generated. Additionally, downloaded files (package distributions) are also cached.

Debugging Issues #

If you encounter issues with package sources, one of the simplest steps you might take to debug an issue is rerunning your command with the --no-cache flag.

poetry --no-cache add pycowsay

If this solves your issue, you can consider clearing your cache using the cache command.

Alternatively, you could also consider enabling very verbose logging -vvv along with the --no-cache to see network requests being made in the logs.