why does each plugin get its own dedicated virtual...
# getting-started
m
why does each plugin get its own dedicated virtual environment? I’m looking at the CLI documentation for
add
- it mentions that this is the behavior but doesn’t give any information about why it’s this way. I searched this Slack and found this message and thread with more context, but I’m still having a hard time understanding.
e
TL;DR: To avoid any dependency conflicts It’s common practice when installing Python-based tools and apps (as opposed to libraries) to use a dedicated venv for each. It’s the philosophy followed by pipx
m
hmm, thank you - that’s very helpful (thinking of these plugins as applications rather than libraries).
I think that’s the “aha!” moment I was looking for
c