You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking into library updates and #2150 would be helpful by displaying the same data pip generates. That is just partially what I need.
I decided to open a new thread since the last comment there was about people hijacking it for other requests and I don't want to disturb it further.
UV evolved so much since the --outdated flag was proposed, I believe it is best if there is both an "uv pip" interface (legacy) and a modern version for apps taking advantage of "uv sync" et al. Or just the modern version since uv proved it is not just a "fast pip". The legacy version could be just a byproduct or specialization of this for the sake of pip completeness.
My proposal is:
Provide a high level "info" or "metadata" command where it can output any known information about a package or the installed packages. It would be a superset of uv pip show and uv pip list
One feature that is important to me is to know how far apart the versions are by checking the release date. Some project move from semver to calendar versioning so you jump from e.g. 2.0 to 24.8. Seeing release dates may seem less scary.
Another reason would be to find stale or dead projects. This would be an awesome use case. If you are up to date, but latest version is from 2017 it is time to replace the dependency.
Show the actual package metadata so you don't need to browse pypi
$ uv info django==5.1.1 --metadata
Metadata-Version: 2.1
Name: Django
Version: 5.1.1
Summary: A high-level Python web framework that encourages rapid development and clean, pragmatic design.
Author-email: Django Software Foundation <foundation@djangoproject.com>
License: BSD-3-Clause
...
One last useful thing would be support for multiple formats, such as JSON for integrating UV into pipelines.
This command (specially the --released option) would pair quite well with the --exclude-newer global parameter.
The text was updated successfully, but these errors were encountered:
I was looking into library updates and #2150 would be helpful by displaying the same data pip generates. That is just partially what I need.
I decided to open a new thread since the last comment there was about people hijacking it for other requests and I don't want to disturb it further.
UV evolved so much since the
--outdated
flag was proposed, I believe it is best if there is both an "uv pip" interface (legacy) and a modern version for apps taking advantage of "uv sync" et al. Or just the modern version since uv proved it is not just a "fast pip". The legacy version could be just a byproduct or specialization of this for the sake of pip completeness.My proposal is:
Provide a high level "info" or "metadata" command where it can output any known information about a package or the installed packages. It would be a superset of
uv pip show
anduv pip list
One feature that is important to me is to know how far apart the versions are by checking the release date. Some project move from semver to calendar versioning so you jump from e.g. 2.0 to 24.8. Seeing release dates may seem less scary.
Another reason would be to find stale or dead projects. This would be an awesome use case. If you are up to date, but latest version is from 2017 it is time to replace the dependency.
Show the current installation (superset of
uv pip show
). Should also support--released
next to version numberShow the actual package metadata so you don't need to browse pypi
One last useful thing would be support for multiple formats, such as JSON for integrating UV into pipelines.
This command (specially the --released option) would pair quite well with the
--exclude-newer
global parameter.The text was updated successfully, but these errors were encountered: