Broken references in Virtualenvs

Question

I recently installed a bunch of dotfiles on my Mac along with some other applications  I changed to iTerm instead of Terminal  and Sublime as my default text editor  but ever since  all my virtual environments have stopped working  although their folders inside  virtualenvs are still there and they give the following error whenever I try to run anything in them   dyld  Library not loaded   executable path     Python   Referenced from   Users  user   virtualenvs modclass bin python   Reason  image not found Trace BPT trap  5   I have removed all the files related to dotfiles and have restored my  bash profile to what it was before  but the problem persists  Is there any way to diagnose the problem or solve it in an easy way  e g  not requiring to create all the virtualenvs all over again

User · Answer

It appears the proper way to resolve this issue is to run

 pip install --upgrade virtualenv

after you have upgraded python with Homebrew.

This should be a general procedure for any formula that installs something like python, which has it's own package management system. When you install brew install python, you install python and pip and easy_install and virtualenv and so on. So, if those tools can be self-updated, it's best to try to do so before looking to Homebrew as the source of problems.

User · Answer

I had a broken virtual env due to a Homebrew reinstall of python  thereby broken symlinks  and also a few  sudo pip install s I had done earlier  Weizhong s tips were very helpful in fixing the issues without having to reinstall packages  I also had to do the following for the mixed permissions problem   sudo chown -R my username lib python2 7 site-packages

User · Answer

A update version  Chris Wedgwood s answer for keeping site-packages  keeping packages installed   cd    virtualenv name of broken venv   mv lib python2 7 site-packages        rm -rf  Python bin lib include virtualenv   rm -rf lib python2 7 site-packages mv   site-packages lib python2 7

User · Answer

Virtualenvs are broken  Sometimes simple way is to delete venv folders and recreate virutalenvs

User · Answer

I found the solution to the problem here  so all credit goes to the author   The gist is that when you create a virtualenv  many symlinks are created to the Homebrew installed Python   Here is one example     ls -la    virtualenvs my-virtual-env     lrwxr-xr-x  1 ryan staff   78 Jun 25 13 21  Python - gt   usr local Cellar python 2 7 7 Frameworks Python framework Versions 2 7 Python       When you upgrade Python using Homebrew and then run brew cleanup  the symlinks in the virtualenv point to paths that no longer exist  because Homebrew deleted them    The symlinks needs to point to the newly installed Python   lrwxr-xr-x  1 ryan staff   78 Jun 25 13 21  Python - gt   usr local Cellar python 2 7 8 1 Frameworks Python framework Versions 2 7 Python   The solution is to remove the symlinks in the virtualenv and then recreate them   find    virtualenvs my-virtual-env  -type l -delete virtualenv    virtualenvs my-virtual-env   It s probably best to check what links will be deleted first before deleting them   find    virtualenvs my-virtual-env  -type l   In my opinion  it s even better to only delete broken symlinks  You can do this using GNU find   gfind    virtualenvs my-virtual-env  -type l -xtype l -delete   You can install GNU find with Homebrew if you don t already have it   brew install findutils   Notice that by default  GNU programs installed with Homebrew tend to be prefixed with the letter g  This is to avoid shadowing the find binary that ships with OS X

User · Answer

I recently faced this  None of the above solutions worked for me  Seems it wasn t actually Python s problem  When I was running  aws s3 ls I was getting following error   dyld  Library not loaded   executable path     Python This means  the library aws executable is pointing towards is either doesn t exist or is corrupted  thus I uninstalled and reinstalled aws-cli following instructions from this link and it worked

User · Answer

If you using pipenv  just doing pipenv --rm solves the problem

User · Answer

I am sure I am late to the party but I want to say that the resolution of this problem is much simpler than discussed here   You can easily regenerate the virtual environment without having to delete edit anything  Assuming that your broken environment is called env to fix you can just to the following   mkvirtualenv env to fix   This will regenerate the links and fix the environment without the need to dump the current status somewhere and restore it

User · Answer

The accepted answer does not work for me  the file  WORKON HOME   bin python2 7 is no longer a symlink  it is a full-fledged executable     file  WORKON HOME   bin python2 7  Users sds  virtualenvs     bin python2 7  Mach-O 64-bit executable x86 64       The solution is  alas  to completely remove and re-create from scratch all the virtual environments   For the reference   deactivate pip install --user virtualenv virtualenvwrapper pip install --user --upgrade virtualenv virtualenvwrapper for ve in   lsvirtualenv -b   do     assume that each VE is associated with a project     and the project has the requirements txt file   project   cat  WORKON HOME  ve  project    rmvirtualenv  ve   mkvirtualenv -a  project -r requirements txt  ve done

User · Answer

I came across the same issue when I was pointing my python run time from 2 to 3 on my mac  pointing the alias python to python 3 path  I then recreate a new virtualenv and re-install those packages i need for my project  For my use case i have had a python program writing to google sheet  Clean up a few packages that are different from python 2 implementation and wa la  things started working again

User · Answer

This occurred when I updated to Mac OS X Mavericks from Snow Leopard  I had to re-install brew  beforehand too  Hopefully you ran the freeze command for your project with pip   To resolve  you have to update the paths that the virtual environment points to    Install a version of python with brew    brew install python   Re-install virtualenvwrapper    pip install --upgrade virtualenvwrapper   Removed the old virtual environment    rmvirtualenv old project   Create a new virtual environment    mkvirtualenv new project   Work on new virtual environment   workon new project   Use pip to install the requirements for the new project    pip install -r requirements txt  This should leave the project as it was before

User · Answer

I had a similar issue and i solved it by just rebuilding the virtual environment with virtualenv

User · Answer

virtualenvwrapper instructions  As indicated in the accepted answer  the root cause is likely a homebrew update that means your virtualenv symlinks are pointing at broken python paths - see details here   For each virtual env  you need to reassign the symlinks to point at the correct python path  in brew cellar   Here is how to do it with virtualenvwrapper  Here I am updating a virtual env called  my-example-env    cd   PYTHON ENVS find   my-example-env -type l -delete mkvirtualenv my-example-env   All done

User · Answer

After trying a few things  this worked for me   go to your virtualenv directory  but don t run workon    cd    virtualenv name of broken venv   Now delete these files   rm -rf  Python bin python  lib python2 7   include python2 7   Then to rebuild your venv  run   virtualenv   workon name of broken venv pip freeze   You should now see a list of your installed packages again

User · Answer

Simply upgrading python3 worked for me   brew upgrade python3

User · Answer

If you ve busted python3 just try brew upgrade python3 that fixed it for me

User · Answer

I was facing the same issue after upgrading brew on my OSX Catalina   After trying bunch of stuffs  I find the following is the best and easy solution   At first  delete the virtual env   Optional   find myvirtualenv -type l -delete   then recreate a new virtualenv  virtualenv myvirtualenv   Reference  https   www jeremycade com python osx homebrew 2015 03 02 fixing-virtualenv-after-a-python-upgrade

User · Answer

All the answers are great here  I tried a couple of solutions mentioned above by Ryan  Chris and couldn t resolve the issue  so had to follow a quick and dirty way    rm -rf  lt project dir gt   or mv  lt project dir gt   lt backup projct dir gt  if you want to keep a backup  git clone  lt project git url gt  Move on    Nothing novel here  but it makes life easier

User · Answer

If this was caused by a brew upgrade that upgraded its Python  and you re ok with downgrading to the previous version  try brew switch python  previous version   eg brew switch python 3 6 5  From here

User · Answer

What fixed it for me was just uninstalling python3 and pipenv then reinstalling them   brew uninstall pipenv brew uninstall python3 brew install python3  brew install pipenv

User · Answer

So there are many ways but one which worked for me is as follows since I already had my requirements txt file freeze  So delete old virtual environment with following command use deactivate cd    rm -r old virtual environment to install virtualenv python package with pip use pip install virtualenv then check if it s installed correctly use virtualenv --version jump to your project directory use cd project directory now create new virtual environment inside project directory using following use virtualenv name of new virtual environment now activate newly created virtual environment use source name of new virtual environment bin activate now install all project dependencies using following command use pip install -r requirements txt

User · Answer

Using Python 2 7 10   A single command virtualenv path-to-env does it  documentation    virtualenv path-to-env Overwriting path-to-env lib python2 7 orig-prefix txt with new content New python executable in path-to-env bin python2 7 Also creating executable in path-to-env bin python Installing setuptools  pip  wheel   done

User · Answer

Anyone who is using pipenv  and you should   can simply use these two commands     without having the venv activated   rm -rf  pipenv --venv    remove the broken venv pipenv install --dev     reinstall the venv from pipfile

User · Answer

I tried the top few methods  but they didn t work  for me  which were trying to make tox work  What eventually worked was   sudo pip install tox   even if tox was already installed  The output terminated with   Successfully built filelock Installing collected packages  py  pluggy  toml  filelock  tox Successfully installed filelock-3 0 10 pluggy-0 11 0 py-1 8 0 toml-0 10 0 tox-3 9 0

User · Answer

The problem for me a MacOS user  is that brew updated the Python and virtualenvs links to the old version which was deleted   We can check and fix it by   gt  gt  ls -al    virtualenvs  lt your-virtual-env gt   Python  Python - gt   usr local Cellar python  lt old-version gt  Frameworks Python framework Versions 3 7 Python  gt  gt  rm    virtualenvs  lt your-virtual-env gt   Python  gt  gt  ln -s   usr local Cellar python  lt new-version gt  Frameworks Python framework Versions 3 7 Python    virtualenvs  lt your-virtual-env gt   Python

User · Answer

When you are running into this issue on a freshly created virtualenv  it might be that your python version installed by brew is  quot unlinked quot   You can fix this for example by running  brew link python 3 8  but specify your speficic python version  You can also run brew doctor  it will tell you if you have unlinked stuff and how to fix this

[python] Broken references in Virtualenvs

Examples related to python

Examples related to macos

Examples related to virtualenv

Examples related to homebrew

Examples related to dyld