Member Site › Forums › PyRosetta › PyRosetta – Build/Install › How to get PyRosetta on OS X 10.6.6 working successfully
- This topic has 1 reply, 1 voice, and was last updated 13 years, 2 months ago by Anonymous.
-
AuthorPosts
-
-
October 24, 2011 at 10:22 pm #1064Anonymous
Hello all,
I thought I would post this here to help other folks installing PyRosetta.
My system is as follows:
OS X 10.6.7
Intel Core 2 Duo – 64 bit (To find out if you have a 64 bit machine go here http://support.apple.com/kb/ht3696)
X-Code installed
Native OSX python1) After you have installed X-code and download PyRosetta open up your terminal and type:
$ which pythonYou should see something like this:
/usr/bin/pythonThen at the command line type:
$pythonYour output should look like this:
Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49)
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type “help”, “copyright”, “credits” or “license” for more information.
>>>>At the >>>> line type hash(‘a’)
>>>> hash(‘a’)
12416037344
>>>If you see that number returned you have python 2.6.x running in 64 bit mode. If not, you need to get the native mac python running in 64 bit mode (but check to make sure your machine is actually capable of running in 64 bit).
One thing I had to do was to remove ALL other versions of python installed. It’s important to remove all the symbolic links and framework libraries. DON’T remove the native OS X python. Also the macports, fink, and official python 2.6.x didn’t work on my machine. Macports and fink will place python is weird places on your mac and this will cause problems when you try and run PyRosetta.
The files you might need to remove are here:
/Applications/Python X
/Library/Frameworks/Python.framework/Versions/X
/usr/local/bin/pythonXOnce those are cleared out and you are sure you are running the native OS python you can install and run PyRosetta with no problems. ipython is very handy so I would recommend using that plus linking ipython with emacs for editing.
Hope this helps some folks,
ara -
October 25, 2011 at 4:43 pm #6179Anonymous
I suspect you could just remove the symbolic links in /usr/local/bin/ without having to gut out all your other pythons. I haven’t tried that out.
-
-
AuthorPosts
- You must be logged in to reply to this topic.