Chris Rodrigue

It's tricky enough that other projects like `pdm` have avoided adding this feature. Too many broken corner cases. See the green note here: [Looking for `pdm shell`?](https://pdm-project.org/en/latest/usage/venv/#activate-a-virtualenv)

I have a similar use case to @J3ronimo My org is tied to using vetted Python package distributions such as Anaconda/WinPython in environments that lack access to PyPI. The general...

A cop-out way to get a list of already-satisfied requirements would be to just shell out to `python -m pip list`, but I'm not sure how one would annotate sources...

Just chiming in here to say that I found a need to be able to set a static contrast ratio. The “Automatically adjust lightness of indistinguishable text” setting seems to...

I think you can use `uv venv --system-site-packages` but `uv sync` is not yet aware of requirements that are already satisfied by the system/inherited environment so it still attempts to...

+1 to what @jfgordon2 said. I think supporting `requirements.txt` input and output is wise to maintain compatibility with legacy tooling that isn’t yet caught up with PEP 621. I have...

Taking a CycloneDX BOM as *input* could also be an awesome way to set up a venv. Any python components in the BOM would have a PyPI purl, which uv...

Well, SBOM is a standardized specification describing the dependencies of a software project. It is highly relevant in the realm of security and enables interoperability between various CI/CD tools such...

A `uv export` format option sounds perfect! Notes: The [CycloneDX spec](https://cyclonedx.org/docs/1.6/json/) is currently at version 1.6. It supports really rich metadata, but the only required fields in an SBOM are...

Good news: [PEP 770](https://peps.python.org/pep-0770/) was just accepted, which notably reserves the subdirectory `.dist-info/sboms` Some highlights: > [SBOM files in project formats](https://peps.python.org/pep-0770/#sbom-files-in-project-formats) > >A few additions will be made to the...