It seems that bass is incompatible with virtualenv. The problem is that virtualenv changes the python binary in such a way that python3 -sS can no longer find the installed modules.
~/.c/fish $ bass 'source /usr/local/bin/virtualenvwrapper.sh ; workon angr' 15:55:00
~/.c/fish $ bass 15:55:01
Traceback (most recent call last):
File "/home/ed/.local/share/omf/pkg/bass/functions/__bass.py", line 12, in <module>
import json
ModuleNotFoundError: No module named 'json'
~/.c/fish $ which python3 15:55:02
/home/ed/.virtualenvs/angr/bin/python3
~/.c/fish $ python3 -c 'import json' 15:55:06
~/.c/fish $ python3 -sS -c 'import json' 15:55:12
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'json'
Not a straight answer to this question, but you might find virtualfish a great replacement. I find it even better than the bash equivalent in certain aspects like the connect command.
It seems that bass is incompatible with virtualenv. The problem is that virtualenv changes the python binary in such a way that
python3 -sS
can no longer find the installed modules.