[viraptor]

That comic does more harm than good, I believe. It's an illustration of what happens if you save 15min of learning, by doing 5h of trying random things until they maybe work by accident. If you understand how a venv works, you won't end in that situation in the first place.

[BiteCode_dev]

It's just a comic, it doesn't have to be accurate, and I think it delivers the message.

Besides, "you understand how a venv works" is not that simple.

- if you use anaconda, do you use conda env or something else? This will have huge consequences on the availability of packages and modes of failure.

- do you use virtualenv or poetry? In that case, how do you install them? How do you run them? The answer to this will change depending of your OS.

- do you use homebrew or pyenv? Then you env may just break on you one month later, will you be able to fix it?

- do you use venv? In that case do you know about the "py" command ? Do you know about "-m"? Do you know which packages to install on linux so that it's available?

Last week I was playing with a telegram bot with a friend of mind. I asked why he didn't use a venv. He told me he could never remember how it worked.

He has been running very lucrative a django site for 10 years.