3 ms·
>It shouldn't be a problem though, since you probably will use a virtualenv anyway. virtualenvs don't create a new interpreter, they just fudge the python path
by poooogles 10y ago
>It shouldn't be a problem though, since you probably will use a virtualenv anyway.
virtualenvs don't create a new interpreter, they just fudge the python path?
Definitely not recommended on interpreted languages (although we use it all the time on our go apps).
- m45t3r 10y agoThey create a copy of the binary of the interpreter, you can even call it directly instead of activating the virtualenv first.