Add 'package' manager to Python built-in CLI tool

[notatallshaw (Damian Shaw)]

@MegaIng

Such tools already exists! E.g. uv. Now you just need to convince linux distros to provide it, which has nothing to do with python.

IMO it’s more important what the PSF decides to distribute, most third party distributors will take their cues about Python from the PSF. I think uv would not be the PSFs first choice, and there are other options such as hatch and poetry.

But there would need to be an open discussion about what requirements would be needed from such a tool, and I think it would make sense for a consensus about this to come from the PyPA first. But such discussions have been shot down by core developers in the past: Why doesn't pip write installed packages to pyproject.toml? - #10 by notatallshaw

@MegaIng

Note that the “chain-of-pain” you are describing is very specific to some linux distros and doesn’t exists at all on e.g. windows - just install uv, then create your python project.

A similar chain of pain exists on Windows if I’m only allowed to use OS provided tools, even on the happy path (and I’ve seen several windows store specific errors reported to pip, so I’m not sure that the happy path is as likely as it is on Linux):

Type python in cmd window → Install “Python” from Windows store → Open a new cmd window → Create venv → Upgrade pip with pip → Install uv with pip → Install uv at user level with uv → Deactivate venv → Delete venv → Install Python and/or create project with uv

@MegaIng

I think it’s better to take OP at their word and believe that what they want is actually a packager manager integrated into the python command.

OP also said this:

@nkpln

Go has go mod tool and Rust has cargo

Neither of those tools are part of their respective standard libraries. So I believe there is confusion about OP actually means/wants, hence my post explaining there is confusion.