You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was surprised to notice that on a Macbook M1, if I install virtualenvwrapper via brew install virtualenvwrapper that the python module doesn't pick it up. For it to work, I have to explicitly call source .virtualenvwrapper.sh and ain't nobody got time for 'dat!
Looking at the python module here in Prezto, I expected it to automatically discover the presence of the virtualenvwrapper.sh file and source it:
But while that works, I actually think it'd be slightly cleaner to be able to brew install virtualenvwrapper... or rather, regardless of where it's coming from, if my path is setup such that I can call which virtualenvwrapper.sh, then I'd expect prezto to source that...
I was surprised to notice that on a Macbook M1, if I install
virtualenvwrapper
viabrew install virtualenvwrapper
that thepython
module doesn't pick it up. For it to work, I have to explicitly callsource .virtualenvwrapper.sh
and ain't nobody got time for 'dat!Looking at the python module here in Prezto, I expected it to automatically discover the presence of the
virtualenvwrapper.sh
file and source it:prezto/modules/python/init.zsh
Lines 138 to 144 in 9195b66
I did notice on a M1 Macbook that since Homebrew uses a different path than intel macs, that may be the problem:
But when I tried locally hardcoding the different path, it didn't seem to work:
The text was updated successfully, but these errors were encountered: