|
|
|
|
|
|
by CaliforniaKarl
251 days ago
|
|
|
I'm not a Rustacean, but I'll tell you what merited me installing uv (via its MacPorts package) last week. I had decided to do something via a one-off Python script. I wanted to use some Python packages for the script (like `progressbar2`). I decided to use Inline Script Metadata[0], so I could include the package dependencies at the top of the script. I'm not using pipenv or poetry right now, and decided to give uv a try for this. So I did a `sudo port install uv`, followed by a `uv run myscript.py --arguments`. It worked fine, making & managing a venv somewhere. As I developed the script, adding & changing dependencies, the `uv run …` installed things as needed. After everything was done, cleanup was via `uv cache clean`. Will I immediately go and replace everything with uv? No. As I mentioned in another post, I'll probably next look at using uv in my CI runs. But I don't feel any need to rush. [0]: https://packaging.python.org/en/latest/specifications/inline... |
|
|