-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discuss uv
and add it to the website.
#419
Comments
I'm using it and it is super quick. I was using https://github.com/tox-dev/tox-uv, but it was very buggy, not sure if that was |
## Solves - #443. Deliberately does not address - #419. Even if we decide to recommend `uv` over `conda-forge` we want to make the distinction. Picky comments about language and clarity very gratefully received. --------- Co-authored-by: David Stansby <[email protected]> Co-authored-by: David Pérez-Suárez <[email protected]>
Notes from hackmorning 2024-10-22
DiscussionThe "problem" with
Relating to
Research computing people (@heatherkellyucl @ikirker 👋) strongly discourage SummaryIf you're new to the game you should use DecisionsWe will replace
Add |
This was a good read @samcunliffe @matt-graham https://til.simonwillison.net/python/uv-cli-apps |
Could change the installation command to uvx cookiecutter gh:UCL-ARC/python-tooling --checkout latest |
Yeah. See Matt's suggestion on my PR. Shall we make a new issue? I also think we could simplify the instructions a bit. And perhaps they should be above the avatars? |
Yeah maybe, it does seem a nice one liner for newbies |
I've attempted to simplify the user-facing quick-start instructions. Not a huge fan of enumerated instructions and the optional (but cool) one-liner it doesn't really fit in 1. 2. 3.... Also it's a bit overkill to have a venv/conda environment just for cookiecutter itself. The cookiecutter docs recommend `pipx install`. I claim that we want to encourage `uvx` because it's fast and cool 😎 . I've spent a bit of effort trying to be clear but comments on clarity etc are very welcome. I also moved and merged the dev instructions into CONTRIBUTING so README is _**just**_ user-facing. And CONTRIBUTING is just dev. This addresses - #466 And two comments - #464 (comment) - #419 (comment) --------- Co-authored-by: David Stansby <[email protected]> Co-authored-by: Patrick J. Roddy <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Which Section of the Documentation Needs Improving?
We should decide on a traffic light for
uv
and add it to the appropriate doc page.In case we decide 🟢, we should add it to the template and update docs accordingly.
What Can be Improved About This Section
Add
uv
. Feels like it's at least an amber 🟠.How to Improve This Section
No response
The text was updated successfully, but these errors were encountered: