3 ms·

I use this frequently on Windows and Linux. These are the steps I take: $> uv init --script <script_name>.py $> uv add --script <script_name>.py <pkg1> <pkg2>

I use this frequently on Windows and Linux. These are the steps I take: $> uv init --script <script_name>.py $> uv add --script <script_name>.py <pkg1> <pkg2> ... $> uv add --script <script_name>.py --dev <dev_pkg1> <dev_pkg2> ... $> uv run <script_name>.py Hope this helps :) Source: https://docs.astral.sh/uv/guides/scripts/ https://docs.astral.sh/uv/guides/scripts/

networked 2y ago
Unfortunately, `uv add --dev` doesn't work with `--script`: > uv -V uv 0.6.10 > uv add --script foo.py --dev ruff error: the argument '--script <SCRIPT>' cannot be used with '--dev' Usage: uv add --script <SCRIPT> --link-mode <LINK_MODE> <PACKAGES|--requirements <REQUIREMENTS>> For more information, try '--help'. There is currently no mention of `uv add --script foo.py --dev ...` in https://docs.astral.sh/uv/guides/scripts/ https://docs.astral.sh/uv/guides/scripts/. Inline script metadata in Python doesn't standardize development dependencies. I wrote a recent comment about how I develop scripts with `pyproject.toml` to have a regular development environment: https://news.ycombinator.com/item?id=43503171 https://news.ycombinator.com/item?id=43503171.
- quickslowdown 2y ago
  Interesting about the --deb flag not working with scripts. I wrote this from memory and feel like I've installed dev dependencies for a script, but it must be a hallucination because I just tried and it doesn't work. Thanks for the correction.
  - mixmastamyk 2y ago
    Aside: angle brackets should be avoided in shell examples; one mistaken enter and work can be destroyed.