OS X 10.9

[GoogleCodeExporter]

Files should be installed to /Library/Python/2.x/site-packages/ instead of 
/Library/Frameworks/Python.framework/Versions/2.x/lib/python2.7/site-packages/. 
 This script fixes the installation on a stock 10.9:

<code language="bash">
#!/usr/bin/env bash

# move python 2.7 files to a place the system python will look
cd 
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/
sudo cp -R pyo* _pyo* /Library/Python/2.7/site-packages/
sudo rm -R pyo* _pyo*

# move python 2.6 files to a place system python will look
cd 
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/
sudo cp -R pyo* _pyo* /Library/Python/2.6/site-packages/
sudo rm -R pyo* _pyo*
</code>

Original issue reported on code.google.com by colin...@musikara.com on 13 Jan 2014 at 3:35

[GoogleCodeExporter]

The installer should install files in both system installed python and 
python.org framework. I don't have a 10.9 computer, last system I tried was 
10.7 everything was installed correctly... Can you tell me what is the value of 
VERSION after running this line in a bash script?

VERSION=`sw_vers -productVersion | sed -e 's/\.//g'`

It's supposed to give something like '1090'.

Olivier

Original comment by belan...@gmail.com on 19 Feb 2014 at 1:55

[GoogleCodeExporter]

Yea,

I learned the other day that this isn't a 10.9 specific issue.

On my 10.9 virtual machine where the issue occurred:

$ sw_vers -productVersion | sed -e 's/\.//g'
109
$ sw_vers -productVersion
10.9

On another machine where the issue occurred:

$ sw_vers -productVersion
10.7

Weird, I know.  But my shell script fixed the import errors in both cases.

Original comment by colin...@musikara.com on 19 Feb 2014 at 10:30

[GoogleCodeExporter]

Fixed for the next release. The installer will install pyo in both places.

Original comment by belan...@gmail.com on 28 Aug 2014 at 7:07

• Changed state: Fixed