Deno has made its PyPI distribution official

Why is it 2026 and I still can't apt install deno?

OK this is cool:

  uvx deno --version

The wheel comes in five flavors: https://pypi.org/project/deno/#files - Windows x86, manylinux x86 and ARM64, macOS x86 and ARM64.

That's a lot of machines that can now get a working Deno directly from PyPI.

Good news for future yt-dlp releases (cf. https://news.ycombinator.com/item?id=45898407), which could now mark it as an optional dependency available through Python's native packaging.

Can someone please ELI5 what this means for Deno and Python? TFA: "deno is being distributed on pypi for use in python projects" makes it sound like you can now `import deno` and have a JS engine/subsystem in Python, like we finally came full circle from [PyScript](https://pyscript.net/).

However, other comments make it sound like a bunch of other projects have discovered that PyPI is a good distribution channel. Which, to me, sounds like using the Internet Archive as your CDN. Is PyPI the next apt/yum/brew or what?

Quite interesting to observe PyPI being used as a distro agnostic binary package manager. Someone is going to create a NixOs competitor that uses PyPI for hosting and uv for installation.

Putting this here for visibility:

PyPi: https://pypi.org/project/deno/

GitHub: https://github.com/denoland/deno_pypi

(Note that the GitHub link in the first post of the issue linked by this HN post now redirects to the official location, as of the time I write this.)

It would be pretty magical if this simplifies bundling static assets in Python applications, letting us avoid independently installing and running the Node toolchain.

For better or worse, pypi is the executable distribution mechanism of the future.

Other cool tools you can install from pypi:

1. https://pypi.org/project/cmake/

2. https://pypi.org/project/ninja/

3. an entire c/c++/zig toolchain: https://pypi.org/project/ziglang/

4. the nvcc cuda compiler: https://pypi.org/project/nvidia-cuda-nvcc/