I don't get it. Then you just install the tool outside of venv? then it's installed for your user account.
But then all the tool's dependencies have to play nice with the dependencies of all your other unrelated Python-based tools.
One thing you can do (I'm not saying it's user friendly) is set up the tool in a virtualenv and then set up an alias like
alias foo-tool=/home/blah blah/tools/something/env/bin/python -m foo-tool
That requires you to be running the right version of python at the system level, and for all your installed tools to have compatible package versions. It doesn't work very often for me
But then all the tool's dependencies have to play nice with the dependencies of all your other unrelated Python-based tools.
One thing you can do (I'm not saying it's user friendly) is set up the tool in a virtualenv and then set up an alias like
That requires you to be running the right version of python at the system level, and for all your installed tools to have compatible package versions. It doesn't work very often for me