Conversation
There was a problem hiding this comment.
Pull request overview
Adds the uv project to the Packaging Guide’s “Key Projects” summaries, expanding the list of recommended tooling in the Python packaging ecosystem.
Changes:
- Added a new “uv” entry with label anchor, links (Docs/GitHub/PyPI), and a short description of its capabilities.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
woodruffw
left a comment
woodruffw
left a comment
There was a problem hiding this comment.
It seems reasonable to me for this to be included, but in the interest of transparency/conflict avoidance I think another editor should also approve this 🙂
|
@bangseongbeom this PR is approved. Is there anything blocking it from merging? |
|
Maybe @webknjaz? |
|
Yes, it needs someone other than me with the commit bit to approve (to resolve any potential CoI). |
As he mentioned, I'm waiting for approval from the other reviewer. |
| `GitHub <https://github.com/astral-sh/uv>`__ | | ||
| `PyPI <https://pypi.org/project/uv/>`__ | ||
|
|
||
| A Python package and project manager, written in Rust for high performance. It |
There was a problem hiding this comment.
Sounds like it fits the definition of a workflow tool more (it's actually listed as such @ https://packaging.python.org/en/latest/guides/tool-recommendations/#workflow-tools). Perhaps, this should just say it's a workflow tool at the beginning and being a package/project manager/interpreter installer could be a part of the list of things in the last sentence?
There was a problem hiding this comment.
That's fine with me. We don't use that terminology in the uv documentation, but it seems well defined here.
There was a problem hiding this comment.
It's kind of everything except a task runner, which is what I think I'd define as a key part of a workflow tool. You can get away without setting up tasks (much of the time uv run pytest works out-of-the-box in most projects I work on).
Nox/tox/poe/pixi don't seem to be listed here at all, so there's not much to compare with, I think that's what would come to mind for "workflows". In the workflow list, I do see Pipenv, that doesn't have tasks. I don't think flit does either. Poetry does have poe, so maybe. uv is not in that list, by the way, maybe that should be added here too?.
Given that list is pretty general, I think calling it a workflow tool is also fine, but it's also a package and project manager, and I'd say that fits a little better than "workflow", especially without task support. +/- 0.
There was a problem hiding this comment.
Yeah, that list is kinda loosely defined. Other entries in this document also seem to focus more on what the projects do rather than how they're implemented. And so I'm struggling to formalize why this seems to stand out writing style-wise.
Add uv to Project Summaries.
📚 Documentation preview 📚: https://python-packaging-user-guide--2023.org.readthedocs.build/en/2023/