Replies: 2 comments 2 replies
-
|
I highly suggest use of |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Ah, I see you are referring to importable modules and not tools with entrypoints. I think the answer to that question is the same as any other tool -- install things into one or more sandbox/pet virtual envs you keep in a common location. e.g. python3 -m venv ~/.virtualenvs/sandbox
source ~/.virtualenvs/sandbox/activateThere are common tools to support this workflow, like pyenv-virtualenv and virtualenvwrapper. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My current setup is:
pyenvfor multiple python versions, but all clean (with no packages installed)poetryfor project environments managed viapipxThis is a perfect setup for working on multiple projects, as I have separate python versions, environments, etc.
However, many times I have a situation that I'm in a random directory and need to quickly pull up python interactive prompt to verify some random though. Usually a bare python is not enough, I need it to have a bunch of most often used packages pre-installed (e.g. pandas, numpy).
In other words, I need to have a globally accessible python environment for experimenting with random stuff, not related to any particular project.
What's the best way to achieve this, without cluttering the pyenv python interpreters with random packages?
Beta Was this translation helpful? Give feedback.
All reactions