on Recommended way to run my scripts from a venv? · c/python · 1 pts · 2y@Andy The convention is to place the venv in a .venv/ sub folder. Follow the convention! This is shell agnostic Learn pyenv and minimize shell scripts (only lives within a Makefile). Shell scripts within Python packages is depreciated
on Python's UV tool is even better · c/python · 0 pts · 2y@Andy @xantoxis The issue with uv is the same biggest issue that Python faces, maintenance costs. Python coders are not Rust coders. Which is quite the head scratcher. Learning Rust techstack creates an enormous barrier to entry when it comes to adopting, uv. uv main advantage is not speed, it's the override for resolving dependency hell If it didn't bring something more to the table, besides speed, no one would care
@Andy The convention is to place the venv in a .venv/ sub folder. Follow the convention!
This is shell agnostic
Learn pyenv and minimize shell scripts (only lives within a Makefile).
Shell scripts within Python packages is depreciated
@Andy @xantoxis
The issue with uv is the same
biggest issuethat Python faces, maintenance costs.Python coders are not Rust coders. Which is quite the head scratcher.
Learning Rust techstack creates an enormous
barrier to entrywhen it comes to adopting, uv.uv main advantage is not speed, it's the override for resolving dependency hell
If it didn't bring something more to the table, besides speed, no one would care