4 ms·
Has anybody had any issues with homebrew, virtualenv, or prezto (zsh) after a Mavericks install?
by curiouscat321 13y ago
Has anybody had any issues with homebrew, virtualenv, or prezto (zsh) after a Mavericks install?
- res0nat0r 13y agoHomebrew seems to be working fine as I just did a brew update without any problems. I was getting virtualenvwrapper errors upon opening a new terminal because that was gone from /Library/Python I fixed it by doing: easy_install --upgrade pip sudo pip install virtualenvwrapper
- unfamiliar 13y agoI've been running the betas and using homebrew since they were released. No problems after the first few months. You need the new XCode/dev tools for it to work, which are in the app store.
- bdcravens 13y agoNo issues with homebrew. I did have to accept XCode license, as I recently upgraded, but that's unrelated to Mavericks.
- vonseel 13y agoHomebrew is giving me warnings about XCode 5.0 being out of date, but the developer site isn't specifying 5.0.1 as Homebrew is asking for and I don't have an available update in the App Store. I don't usually use sudo to install virtualenv, you can use the method here and it will work: http://stackoverflow.com/questions/4324558/ http://stackoverflow.com/questions/4324558/ I had some trouble reloading an existing vagrant box and virtualbox, seems to have resolved itself after using each providers uninstall tool bundled with the latest versions of Vagrant and Vbox and installing fresh versions after.
- gluttony 13y agoMongodb and CasperJS were broken for Mavericks comes with libc++ instead of libstdc++ by default. A little hack could fix these two.