Terminal issue with virtualenvwrapper after Mavericks Upgrade
After upgrading to OSX Mavericks, I am getting this message in the terminal:
/usr/bin/python: No module named virtualenvwrapper virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python could not import the module virtualenvwrapper.hook_loader, check that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly.
Try reinstalling pip and then reinstalling virtualenvwrapper (I had to go through these steps after upgrading to Mavericks):
$ sudo easy_install pip $ sudo pip install --upgrade virtualenvwrapper
python Terminal issue with virtualenvwrapper after Mavericks , After upgrading to OSX Mavericks, I am getting this message in the terminal: /usr/ bin/python: No module named virtualenvwrapper virtualenvwrapper.sh: There� après la mise à niveau vers OSX Mavericks, je reçois ce message dans le terminal: /usr/bin/python: No module named virtualenvwrapper virtualenvwrapper.sh: There was a problem running the initialization hooks.
Re-arrange the export order so that the
python path is placed before the
virtualenv commands in your
# python path export PATH=/usr/local/bin:$PATH # needed for virtualenvwrapper export WORKON_HOME=$HOME/.virtualenvs source /usr/local/bin/virtualenvwrapper.sh
Problema do terminal com o virtualenvwrapper ap�s o upgrade do , python Terminal issue with virtualenvwrapper after Mavericks Upgrade? brew install python --with-brewed-openssl # Open a new terminal tab now (to access� OSX Mavericks (10.9), but the issue appeared in 10.8 as well (lazy me only got to fixing it now) Whenever I start a new terminal session or source ~/.zshrc I get the following message: zsh virtualenvwrapper plugin: Cannot find virtualenv
Try edit .bash_profile file
# Home brew export PATH=/usr/local/bin:$PATH # virtualenvwrapper export WORKON_HOME=$HOME/.virtualenvs export VIRTUALENVWRAPPER_PYTHON=/usr/local/bin/python export VIRTUALENVWRAPPER_VIRTUALENV=/usr/local/bin/virtualenv source /usr/local/bin/virtualenvwrapper.sh
python — Problema de terminal con virtualenvwrapper despu�s de , Problema do terminal com o virtualenvwrapper ap�s o upgrade do Mavericks virtualenvwrapper.sh: There was a problem running the initialization hooks. Working on a python project in an isolated python environment is recommended so that python modules and packages don’t meddle with that of other projects or even that of the operating system.
I wouldn't recommend running pip with sudo. This was my solution for the same problem (after upgrading to Mavericks).
In essence, uninstall any virtualenv and brewed Python you had before (use
which <command> to check that you removed everything except the system Python in
/usr/bin/python) and cleanly install them once again:
brew install python --with-brewed-openssl # Open a new terminal tab now (to access /usr/local/bin/python) pip install virtualenv pip install virtualenvwrapper
When I upgraded my Mac to OS X Mavericks, a lot of utilities (like , Despu�s de actualizar a OSX Mavericks, recibo este mensaje en el terminal: virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python Sudo easy_install pip $ Sudo pip install --upgrade virtualenvwrapper. 97 Content dated on or after 2018-05-02 (UTC) is licensed under CC BY-SA 4.0. Let me tell you a story. Recently, I realized that I needed to review how to set up virtualenvwrapper on top of virtualenv in Ubuntu 18.04. I have completed this process several of times on different computers, and every time it seems to be just a little bit different than before. I just got a new laptop and on the way home I read several tutorials on “How to set up virtualenvwrapper on
pip install --upgrade virtualenvwrapper will fix the issue but never used
sudo pip this will change system-wide. If pip throws permission errors without
sudo then you should fix those and then try only with
pip install <--upgrade> $(package).
I rather suggest install
homebrew and then install
brew install pip which will install latest stable version of pip for you.
Install homebrew and then run
brew doctor. If there are any warnings fix those(actually brew will tell you how to fixed those).
You may need to remove system-wide python comes with Mac and use
brewto install required versions. Use this to remove system-wide python
brew install pythonor/and
brew install python3to install required python version/s.
pip install --upgrade virtualenvwrapper
Now on never use
sudo piponly use
A guide to prevent pain and suffering while upgrading to OS X Mavericks For each virtualenv you have, run "pip freeze > requirements.txt" while in the brew install python # if you have an error, it's already installed and there's no issue Followed by a panic attack, and then peace after finding your helpful guide. Cheers, 44 Terminal issue with virtualenvwrapper after Mavericks Upgrade; 29 How can I make a trailing slash optional on a Django Rest Framework SimpleRouter;
99 Terminal issue with virtualenvwrapper after Mavericks Upgrade 96 Webpack 4 - How to configure minimize? 54 in express.js, any way to capture request to both json and html in one function?
The Mavericks installer was not accepting the password to unlock FileVault in the installer itself after reboot. It turns out that the password prompt is in QWERTY despite the language input icon indicating that it was in Dvorak. That is a profoundly annoying bug. comex on Oct 22, 2013 [-]
Virtualenvwrapper with Python 3 Many of you will be familiar with virtualenvwrapper , a nice tool to manage more easily your virtual environments.To install it, we will first install virtualenv : $ pip install virtualenv $ pip install virtualenvwrapper
- Are you sure that virtualenvwrapper.sh is supposed to be in /usr/bin/python or have you installed it into a different version of Python (e.g. installed with Homebrew?)
- Yup, I reinstalled pip and upgraded with the python scripts, then used your advice to upgrade virtualenvwrapper. All is well now, much thanks.
- this worked for me, but only after re-installing easy_install as per this post
- And don't source virtualenvwrapper.sh from .bashrc - that is called early in .bash_profile.
- The only one that worked for me on macOS High Sierra. Thanks @Tuan
- What is
- @chrisFrisina Code is a directory inside my /home, you can change it and name as you want to, after creating the directory
- I have the same problem but in the step 3 when I run echo $VIRTUALENVWRAPPER_PYTHON I get usr/bin/python3 <br/> Because in the step 1 I have **usr/bin/python