![]() Homebrew will install the latest Python v2.7.6, while Mavericks ships with v2.7. Install Python with Homebrew instead of using the Python interpreter which ships with Mavericks. Lots of resources on how to do this - see this or this. You need to reinstall XCode and the Command Line Tools to get a compiler. Some OS X Mavericks users have also reported problems with their email systems after upgrading to OS X Mavericks, which Apple is now working to fix with a new update they will be releasing soon. Here are the steps I followed to fix my Python installation: I encountered this issue when trying to install greenlet package using an easy_install'ed version of' pip, but not with the Homebrew installed pip. But, having encountered the same problem after the Mavericks upgrade (and using Python 2.7), I just did a easyinstall readline at the command line, and everything seems to be working again.Do not create a symlink named /usr/bin/gnutar pointing to a different version of tar or a version of. The solution to that problem is to re-install MacPorts using the installer for Mavericks. You'll avoid some compilation errors when installing some packages. Versions of MacPorts built on 10.8 or lower will fail to install packages on Mavericks because of a missing /usr/bin/gnutar. ![]() the Python packages you install will be put in a safe place and you won't need to use sudo to install them.the installation will come with pip installed.I recovered by installing Python using Homebrew. I was installing packages in /Library/Python/2.7/site-packages, which Apple wiped clean when I upgraded to Mavericks. Like Mountain Lion (OS X 10.8) and Lion (OS X 10.7) before it, OS X 10.9 Mavericks is as easy to install as downloading an installer from the Mac App Store and double-clicking. By broke, I mean that Apple wiped out all of the python libraries I've installed - pip, virtualenv, numpy, matplotlib, ipython, pandas, flask, greenlet - all gone. And unlike the earlier Mail patch, this update will install properly even if you are a developer running the GM version of Mavericks. This was a big break - I work in Python almost everyday. With luck, OS X 10.9.1 fixes the remnant issues lurking about. I felt no rush to upgrade - "If it ain't broke, don't fix it!" - but after reading about the new features, particularly the improved support for multiple displays - I decided to give it a shot.Įverything went smoothly - except that my Python installation completely broke. Sadly for me, it took a few hours of farting around the webs and reading through articles where people were not thinking about the problem from a Mac OS X standpoint.Yesterday I decided to upgrade OS X on my Late-2011 Mac Book Pro from 10.7 Lion to 10.9 Mavericks. Luckily for you, the fix will take only seconds. It just flat-out would not load the pages from either or. The other nasty side-effect of this OS update was that Chrome was pitching a fit about those two websites, as well. Those details are not important to solving the problem. Regarding your network errors: I think if multiple machines have the same problem then you should go somewhere else, like to libraries with free wifi to see. It's a problem with the DigiCert certificates used in OS X to verify and, er, whatever the proper technical description is for whatever SSL-type stuff that's going on there. Using the following git command on OS X 10.9.2:įatal: unable to access SSL certificate problem: Invalid certificate chain Another way that provided by some of the Mac users sharing the same problem on reaching their files after upgrading to Mavericks is: go to the Users & Groups. If you have an avocado handy, it won't help much, but it won't hurt, either. Perhaps it will save someone some headaches, especially if they overthink things like I tend to do. This post is the quick story about a couple of hours I lost thanks to a recent update to OS X Mavericks 10.9.2. If the experiment fails, I dump the branch like it never happened. If I want to try something out that will require major fiddling with the code in a project, I branch and fiddle. If I mangle the source code in my project, I can roll it back to a working state. Source code management ("SCM") is s-m-r-t smart and easy as pie (assuming making pies is indeed easy) with git. So, between home and the office, I use both github and bitbucket. At the meltmedia office, we use the gitflow process of source code management to manage our projects and it works wonderfully. When I write code for AVR, Arduino, iOS, OS X or even the web, I stick it in a git repository on (it's free to have many private repos, so check it out) (thank you, Atlassian!).
0 Comments
Leave a Reply. |