Geek Answers Handbook

On Mac OS X, do you use shipped python or your own?

At Tiger, I used a custom python installation to evaluate newer versions, and I had no problems with this * . Now Snow Leopard is a bit updated and comes with

$ ls /System/Library/Frameworks/Python.framework/Versions/
2.3    2.5    2.6    @Current
  • What can be considered best practice? Using python that ships with Mac OS X or a custom compiled version, say $HOME.
  • Are there any advantages / disadvantages using one option over another?

My setup was pretty simple so far and looked like this: A custom compiled Python in $HOMEand $PATHthat would first examine $HOME/binand then use my personal version of Python. Also $PYTHONPATHpointed to this local installation. That way, I didn't need to sudo-install packages - virtualenv took care of the rest. Note: I liked this setting, so I was just curious and thought that I was asking a question about the bush.

+5
source share
5 answers

I think it depends on your needs. Personally, I use the latest version for any series (2.5, 2.6, etc.) From MacPorts.

+5
source

, 64- . OS X 32-. MacPorts, .

+2

Python, , , . Python Fink MacPorts, .

Python (Fink MacPorts) , (, C). , Python, , , Python, OS X. , , .

+1

, , . , , , .

0

.

/ python . , C, python 3 . (, /tmp ), python. , script/wrapper.

My point of sending our own python distribution is to make sure that when you transfer the application and is not dependent on the installation of the python operating system, there is no weirdness when changing the set of parameters.

It is also not documented anywhere in python docs.

I already found this post 4206511

0
source

More articles:


All Articles