Any binary dependency you have would need to be present for all target architectures in your virtualenv for this to work. But when you pip install a package only the binary for your current platform gets installed.

I presume you'd have the same problem with the binary, there'd have to be separate builds for arm, x64, etc.

There are separate static builds for aarch64 and x86_64, those are put into a "fat binary" that runs on current generation hardware/software combos (osx with aarch64, win with x86_64 and linux with both). Just building for two things is better than figuring out the whole matrix of OS vs architectures which was the other option.

For other architectures like Power/armv7/i686 the software can run using the Blink project [0] [0] https://github.com/jart/blink

If you are distributing software to an audience who want to use your thing without having to build it, then something like this is much more appealing than virtualenv.