Mavericks

Upgraded to OSX Mavericks last night, with a little apprehension. Past upgrades have usually broken all sorts of things with my development environment so the next day is spent trying to get my local Django, Python and everything else straightened out. I couldn’t afford to have a bunch of downtime right now though as I have a huge project going on at work that is going to launch in a few weeks.

But I took the chance anyway and upgraded and I was very happy this morning to only be facing one error. When I opened iTerm I had an error that said:

Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named virtualenvwrapper.hook_loader
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/local/bin/python and that PATH is
set properly.

I guess I can understand why some path issues would be presenting themselves. After looking up a few questions on Stack Overflow that dealt with the issue by uninstalling and reinstalling a bunch of stuff I had a mind panic attack. What the H was I thinking!

After thinking about it a moment I decided to start at the lowest level to try and fix my error. In this case it’s just virtualenvwrapper that is complaining. So lets just reinstall that and see how it goes.

pip install -U virtualenvwrapper

That reinstalled virtualenv as well and boooya - eveything is working as expected. No need to reinstall pip and all that junk. Back to work. Oh, and love the new Mavericks features. I think it’s time to try Safari again.

Update: After working a few hours with my new OS I’ve got a giddy smile on my face. I work with a second monitor at work and the new monitor support is amazing. So awesome to have the top bar on each screen! No more mousing back over to the main screen to get to the program menu. Love you Apple.

comments powered by Disqus