Poetry should offer a task runner. It should be similar to poethepoet, but probably less low-level. Investigate further before implementing. Reference: PDM.

As in the title, Poetry should use findpython to discover available Python versions.

Address python-poetry/poetry#707

most likely based on blinker
Hook functions should receive a proper state of command.

• separate files sending (currently error on sending one of the files fails for both which makes it difficult to resend failed files for the same version later)
• improve error handling (raw HTML sometimes printed to console)
• python-poetry/poetry#2517
• gather metadata from artifacts rather than pyproject.toml

Refactor networking code in Poetry. Poetry should have a custom HTTP client class that is used throughout the code, so that all requests made by Poetry share the settings (like user agent information). This should also introduce a layer of library independence, making it easier to switch to another networking library if needed.

Create setup-poetry action, similar to what PDM offers, but skip the PEP 582 support (obviously).

(similar to PDM)
Poetry should be aware of the way it was installed.
Homebrew: libexec in path
pipx: check pipx venvs in path
installer script: script should add a marker file to installation path?

Those installation methods should be checked when user tries to poetry self update and suggest the proper way. See #6 for more info.

Poetry should notify user about new version of itself being available. This should have a flag in CLI and config to disable the information. Version information should be cached (maybe a configurable cache timeout?). This should be connected with #6.

Currently, while building artifacts, the config_settings option from PEP 517 API is being ignored by poetry-core. It should be passed to the builders for further usage.

Poetry should notify user when cached artifact is being used during installation. Similar to how the info about downloading wheels is being displayed in logs. Information should probably be also displayed on installation list (like Installed <dependency> (<version>) (cached)).

Poetry should have a setting checking the version of itself against the project requirement of Poetry version.

[tool.poetry]
...
poetry-version = ">=1.6"

Introduce "actions" concept. That will be an implementation of the current CLI functionality as code. That will allow for the CLI framework independence and offer commands as plugin API, skipping the CLI stack.

As in the title. Use installer and build.

Followup/connected to #5.

Poetry should suggest a proper way of upgrading itself when using poetry self update. If an installation method can not be detected (or is ambigious) Poetry should ask user if it should proceed or abort (default, with a proper message about the risk; optional --force flag should be considered).

Add --check flag that should run check command before building.
Add --clean flag to cleanup build directory before building new artifacts. (python-poetry/poetry#1329).

See python-poetry/poetry#3827, python-poetry/poetry#1990, python-poetry/poetry#2134

show command should produce a report detached from CLI, so that it can be later displayed on CLI or rendered to JSON/CSV for other tools to analyze easily.

There is also an implementation of dict to CLI Tree inside the current state. This should be extracted to Cleo as a generic component (delegated to trag1c).