Export uv.lock to requirements.txt

[charliermarsh]

No description provided.

[mikeleppane]

+1

After using Poetry for years, I've decided to try uv. And it's great 👏. Here are some thoughts I had while using uv. Some of these may have been discussed already.

• export only dev-dependencies from uv.lock to requirements-dev.txt (this is useful at least in the CI); poetry export --without-hashes --without-urls --only=dev -o requirements-dev.txt
• uv sync/pip install only dev-dependencies (like above useful in the CI)
• show the latest version but only for outdated packages; poetry show --outdated / poetry show --outdated --only=dev has been useful.
• how do get info about the current virtual env? E.g. Poetry has poetry env info command to display info about current env
• is it possible to only update dev-dependencies like poetry update --only=dev?

Thanks!