`uv` works great on a local computer, but there's a few issues and pitfalls for it work correctly on the systems. Blocking issues: - [ ] `uv` must not install `manylinux` packages, see: https://github.com/astral-sh/uv/issues/16540 - [ ] `uv` must see packages installed in other `site-packages` and read `sys.path`, see: https://github.com/astral-sh/uv/issues/16541 - [ ] `uv` must see only installed python and not system python Other issues - [x] not override `--no-config` - [x] must prefer our wheelhouse and still search on PyPI - [x] avoid installing a python version not supported (ie 3.14, 2.7) - [x] does not support our pip config Caveats and Pitfalls - [x] Storage inodes and quotas issue - [ ] `uv run` without a python module would create issues for users - [ ] `uv run script.py` must be ran from the root project directory, else user will run into issues. - [x] our documentation does not document `uv`
uvworks great on a local computer, but there's a few issues and pitfalls for it work correctly on the systems.Blocking issues:
uvmust not installmanylinuxpackages, see: Why it looks like uv is not respecting the manylinux config from PYTHONPATH astral-sh/uv#16540uvmust see packages installed in othersite-packagesand readsys.path, see: Why uv does not seems to see python packages installed in a different site-packages astral-sh/uv#16541uvmust see only installed python and not system pythonOther issues
--no-configCaveats and Pitfalls
uv runwithout a python module would create issues for usersuv run script.pymust be ran from the root project directory, else user will run into issues.uv