Our current approach at making virtualenvs fails if the user is running beam from a uv-installed virtualenv, as the shared libraries are not appropriately linked at the time of creation (and thus ensurepip fails). I'd quite like to support this given uv's popularity (and my own use of it), but it looks like it might be quite a faff (with some uv-specific workaround for patching in the libraries)...
Our current approach at making virtualenvs fails if the user is running
beamfrom auv-installed virtualenv, as the shared libraries are not appropriately linked at the time of creation (and thusensurepipfails). I'd quite like to support this givenuv's popularity (and my own use of it), but it looks like it might be quite a faff (with someuv-specific workaround for patching in the libraries)...