Hello @Cologler. Thank you for your feature request. We'll take a look on it.

There is a "cart before the horse" issue here depending on the OS.

MacOS can install pipx with brew, but Linux and Windows must use python (see the docs here). Hence, you have to install python to install pipx and then poetry all before you can run actions/setup-python, by which point you've already installed python...?

I believe the action should install poetry as a post-step if cache: poetry is used and set up the cache.

There is a "cart before the horse" issue here depending on the OS.

Oops, I forgot about pre-installed software on each runner, and they all have python and pipx. My mistake...

There's a more general use-case here that would be very useful to me, where setup-poetry could install a list of global/system tools via pipx, such as: Poetry, Tox, PDM, Invoke, Poe, etc. The idea being for a way to express pipx-installable tools (and their versions) that setup-python would then take care of installing, including caching the respective virtualenvs (eg /opt/pipx/venvs/) and command (eg /opt/pipx_bin/).

An extra bonus would be a way to express this in the pyproject.toml (as an alternative to passing as input) through a field like [tool.setup-python.pipx] or something like that.

I intend to write a stand-alone action as a proof-of-concept and will report back.

Here is an action I've published to fill this need: https://github.com/BrandonLWhite/pipx-install-action

I do envision that one day this functionality is incorporated directly in actions/setup-python, but until then, please try out my action and see if it meets your needs!

Hello @Cologler. Thank you for your feature request. We'll take a look on it.

Will you accept a PR with this feature? With one more input: "cache-packet-manager: BOOL".

Hello Everyone, Thank you for your suggestion! Currently, setup-python automatically installs pip as it is a core part of the Python ecosystem. Adding support for other package managers like Poetry could introduce unnecessary complexity and maintenance overhead, as this action is designed specifically for setting up Python environments.

Supporting additional tools would also increase the scope of the action, potentially introducing compatibility issues and testing challenges. By keeping Poetry installation as a separate step, users can maintain flexibility and choose the installation method that best suits their needs without affecting the simplicity of the setup process.

We recommend keeping Poetry installation separate to preserve the focus and efficiency of setup-python.

Clearly python is just a second class citizen in actions. Javascript has support for a bunch of different pacakge managers and is generally orders of magnitude faster at setup.

Hello @MrLoh, Thanks for sharing your perspective. We understand the comparison with JavaScript tooling and the desire for broader support within setup-python. Our goal is to keep the action lean, stable, and focused on setting up Python itself, while allowing users the flexibility to choose and manage additional tooling like Poetry as needed.

That said, we’re always open to feedback and will continue to explore ways to improve the Python developer experience in Actions, including setup performance and extensibility.