Yes, you should use a Python venv in a container like docker
Yes, you should use a Python venv in a container like docker
Brought to you by "/r/python answers are so bad I had to write this"
You're viewing a single thread.
Soon, you won't have a choice because major distros are adopting PEP 668. This will make pip install fail in the default system Python and show an error telling you to use a virtual environment.
Well, if this is true then why bother convincing people ;)
So ... if I want to use a python module like, for example, mcstatus in a live shell for convenience I first need to create a venv, activate it, install the package and then use it? And then either have dozens of venvs somewhere or remake them every time?
I am not sure what you mean. Once you created a venv you can always reuse it.
Yes, but it has to be somewhere. I don't want dozens of venv dirs in my homedir.
Then create one venv for everything
the one venv to rule them allis not a viable solution.Some packages cause problems, one tactic is to isolate the problem package into a separate venv.
For example
.venv/-- main venv for the dev setup.doc/.venv- Sphinx docs (now minimum py310).wthfor e.g. package restview which has out of date dependencies.Each venv has its respective requirements files. Some associated with a dependency or optional dependency. The ones that aren't are pin files.
Lets say there are easily a total of 20 requirements and constraints (pin files).
This mess is in a freak'n nasty multi level hierarchy.
Now imagine you are the author maintainer of 10 packages. Can you be confident one package requirements won't conflict with other packages requirements?
Almost forgot
these packages are no longer maintained:
pip-tools
pip-requirements-parser
... scary
Can you create venvs inside venvs? That sounds like stuff is going to break tbh.
Why would you want a venv "inside" a venv? What would that mean?
Well, if you want to have Pip-installed tools available generally (e.g. until distros started screwing it up,
pipwas the best way to install CMake), the suggestion was to have a venv for the user that would be activated in your.bashrcor whatever.I think that would work, but then what happens if you want to use a project-level venv, which is really what they're designed for? If you create and activate a venv when you already have one activated does it all work sensibly? My guess would be that it doesn't.
Oh! Hmm. That's a good question and I really don't know. So in other words (this is just how I'm organizing the thoughts in my own head, probably includes some misunderstandings so feel free to correct any you notice) - your "system Python" is really an activated venv specified in your user config in some way, and the question is what happens when you deliberately try to then activate a distinct project venv, which Python executable and collection of installed libraries is invoked when doing stuff with it active?
On the one hand I've never considered that and it's probably a mistake to make too many assumptions about how Python (and its instrumentation,
pipetc. included) are interacting with the OS. Because I know fuck all about that, when I really think about it lol. On the other hand, one of the things I find pleasant about Python is that usually much more informed and thoughtful people than myself have chosen among several ways of dealing with whatever situation I'm thinking about, and have decided on a sensible default. But yep, idk. I originally just thought you misunderstood the idea of a venv lol, to my happy surprise, nope!
This article is about Python venvs using Docker. That I wouldn't want to pollute the base installation on my local machine should be clear.
But you can just create a venv and install everything in there, no need to create dozens of venvs if that's what you want.
just to add to the other answers - no need to have them in your home dir (that sounds like it would suck). use a tool like
uv toolorpipx, or just manually create any venv you need under a path you choose, say$HOME/.cache/venvs/
you can use UV for this use case: https://docs.astral.sh/uv/guides/tools
Yes
Whats the alternative you are advocating for?!
The old way ig
the old way i am fine with
Never ever made a mistake and install anything system wide
don't need white knights or a nanny state to keep us safe
Use pipx or uv --run
Distrobox?
Even with PEP 668, you can still use
pip --break-system-packages