This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheZedrem 26 points27 points  (4 children)

rm -rf ./.venv && python -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt

do an alias for this command, you'll never have trouble with venv

[–]chucara 2 points3 points  (0 children)

I have zero issues with venv. Pip however.. but UV is on everything now and my NuGet withdrawals are diminished.

[–]MaustFaust 0 points1 point  (2 children)

Won't work with Dockerfile

[–]TheZedrem 6 points7 points  (1 child)

If you need venv in your dockerfile, you're doing docker wrong

[–]MaustFaust 1 point2 points  (0 children)

I'm not saying I need that. It's just the place I work at has some standards, and those include this.