11 comments

[ 131 ms ] story [ 591 ms ] thread
I don't get it. Why are python dev environments broken by Mavericks?
I don't know why they should be, but when I restarted my computer after the update I was greeted with a big fat broken virtualenv install, so I wrote this guide to help anyone else with the same problems.
Someone pointed out on HN that Python gives segfault. He used a = 1000, a/1000 example. I did it on Python 3 and got the same error. It worked on Python 2 that came with Mavericks but thats about it. I'd think there are more issues.
I didn't have any problems with the upgrade and neither did anyone in my office. Was this a thing?
It definitely depends on your system configuration. Ideally, it shouldn't break, but however I had it set up was not happy about the upgrade. Did you use the built in Mac python or a new install from Python.org?
A new install. I believe it was a brew as well.
I see he has python via brew. That might be part of it.
Yeah, I had some odd symlink issues.
Didn't have any problem with python after upgrade.
I have found this issue only with CPython 3.3.2. 2.7.5 seems to work fine.