There are currently 570K+ projects in pypi, 60k+ in debian repos.
It can take several months of work to approve one single package to the official repos, for a single distribution. And each have different rules and setup.
Now explain to me how you think this is going to work.
Also, do you place to force everyone to use chroot or containers to replace their virtual env systems to have variations on deps? Or maybe everybody should use nix?
> There are currently 570K+ projects in pypi, 60k+ in debian repos.
Not all PyPi projects require C code.
> It can take several months of work to approve one single package to the official repos
This is a massive exaggeration. For Fedora it takes a couple of days, all of it being necessary review of the code and licenses. And yes, you do have to do that work, it's done by the distros themselves too.
You only need the system package manager to provide the non-Python dependencies of Python packages. I'd expect that those by and large are already packaged in Debian and elsewhere, perhaps with some exceptions among smalltime C (or Rust) projects that only exist to accelerate Python packages.
> Also, do you place to force everyone to use chroot or containers to replace their virtual env systems to have variations on deps? Or maybe everybody should use nix?
Nix is a good fit for this, but so is Guix and probably Spack. With a sane implementation of PEP-725 (which I mention and describe in another comment on this post), users could freely choose whatever package manager they like to supply non-Python deps.
It can take several months of work to approve one single package to the official repos, for a single distribution. And each have different rules and setup.
Now explain to me how you think this is going to work.
Also, do you place to force everyone to use chroot or containers to replace their virtual env systems to have variations on deps? Or maybe everybody should use nix?
Do you want to do that also for JS, Ruby and PHP?