Yep, and from reading this thread it’s also clear that it’s not just uv
(and rye
before it) that is taking that approach but also pdm
and hatch
, so it’s going to be the source of Python for increasing numbers of users.
Official binaries were also noted as something that a better solution for Microsoft Store Python would ideally make use of.
Maybe even conda would switch to using official binaries should they exist (though perhaps there’s some technical differences in their interpreters that I am ignorant to).
It seems like adding official binaries would be a good first step that would enable or improve many of the ways that Python is already currently obtained.
Then a lightweight installer that can be downloaded from python.org that installs said binaries might be really nice for completely new users, but that could be a second step to be considered separately and on its own merits. Or even a more capable official Python management tool, as floated in the MS Store thread. All easier with official binaries available.
Maintenance workload is naturally a factor but there is already developer time being spent on maintaining such binaries, right? – just not under the official Python umbrella. Perhaps the folks who work on the
indygreg/python-build-standalone
builds would be up for helping out/transferring their efforts. The uv
devs have also contributed significantly to that project, and would presumably rather be using and contributing to upstream “real” Python.