Comments on: mysql-python and Snow Leopard

By: kcallahan

Wed, 21 Jul 2010 11:24:11 +0000

This worked for me …

# cd /Developer/SDKs
# sudo ln -s MacOSX10.5.sdk MacOSX10.4u.sdk

By: j-m15

Tue, 06 Apr 2010 03:54:52 +0000

For the sake of sanity, make sure to use sudo and check python to see if you’re running the correct one if you just installed the newest python. Best way to check it’s archs is to type “file $(which python)” without the quotes and it will tell you. Also be sure that typing “file $(which mysql)” also shows whichever arch type you’re going for. It really does matter if your arch types are different, I’ve spent many hours fiddling with this more than once.

By: Sophomore Dev » Creating my first complete Django project on Snow Leopard

Sophomore Dev » Creating my first complete Django project on Snow Leopard — Mon, 18 Jan 2010 19:48:44 +0000

[...] dice, still not working. Poking through the comments of the post above, I came across this indicating that re-building doesn’t actually do it from scratch and you need to go into the [...]

By: bialecki

Mon, 18 Jan 2010 07:58:07 +0000

@jkeane (re comment #24), manually deleting the contents of the build directory fixed my problem with the import error. Really annoying, but thanks for the tip.

By: ssteiner

Thu, 31 Dec 2009 14:46:31 +0000

I had the same problem, then noticed that I was installing with ’sudo’ while building as my regular user.

See: http://websaucesoftware.com/blog/?p=461 and part 2 at http://websaucesoftware.com/blog/?p=462

No need to change to 32 bit mode and screw everything up, just install the one with the right architecture!

By: WombatNation » MySQL Support from Python on OS X

WombatNation » MySQL Support from Python on OS X — Wed, 30 Dec 2009 01:10:20 +0000

[...] Update 12/27/2009: With MySQL 5.1.41 and Snow Leopard (OS X 10.6), you no longer need to create the lib/mysql directory with symbolic links as described in the above article. Also, since Snow Leopard comes with Python 2.6, the path above for Eclipse should be /Library/Python/2.6/site-packages. I found Geert’s instructions to be quite helpful for Snow Leopard. There’s also a lot of useful info here. [...]

By: gelliott

Fri, 04 Dec 2009 18:25:02 +0000

ok, as of dec 3, here is how i got it to work (assembling all the info so far into one spot):

versions:
mysql adapter for python: 1.2.3c1
mysql: 5.1.41 32-bit version
default python for snow leopard: 2.6.1

1.install mysql package: http://dev.mysql.com/downloads/mysql/5.1.html#macosx-dmg

2. grab mysql adapter for python: http://sourceforge.net/projects/mysql-python/files/

3.in directory for mysql for python:
Edit the setup_posix.py and change the following

mysql_config.path = “mysql_config”

mysql_config.path = “/usr/local/mysql/bin/mysql_config”

4. sudo ARCHFLAGS=’-arch i386′ CC=/usr/bin/gcc-4.0 python setup.py build

5. sudo ARCHFLAGS=’-arch i386′ CC=/usr/bin/gcc-4.0 python setup.py install

6. force python to be 32-bit
defaults write com.apple.versioner.python Prefer-32-Bit -bool yes

7. python
Greg-Elliotts-Mac-Pro:~ greg$ python
Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51)
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type “help”, “copyright”, “credits” or “license” for more information.
>>> import MySQLdb
>>>

By: cd34

Thu, 03 Dec 2009 23:29:17 +0000

python setup.py clean doesn’t remove the remnants from your previous failed build.

Try

make clean
python setup.py clean

and build it again, or, worst case, remove and unpack the .tgz again and build with the command line you used. I believe the problem exists because you have some .o files from a previous build.

By: m593026

Thu, 03 Dec 2009 23:24:42 +0000

I had to massage one of the lines that was failing (the infamous 10.4u sdk one) into this:

gcc-4.0 -isysroot /Developer/SDKs/MacOSX10.6.sdk -g -bundle -undefined dynamic_lookup build/temp.macosx-10.3-fat-2.6/_mysql.o -L/usr/local/mysql/lib -lmysqlclient_r -lz -lm -lmygcc -o build/lib.macosx-10.3-fat-2.6/_mysql.so

and it successfully built and installed. I removed the archflags entirely and it worked.

however when i try to import it…:

Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32)
[GCC 4.0.1 (Apple Inc. build 5493)] on darwin
Type “help”, “copyright”, “credits” or “license” for more information.
>>> import MySQLdb
Traceback (most recent call last):
File “”, line 1, in
File “build/bdist.macosx-10.3-fat/egg/MySQLdb/__init__.py”, line 19, in
File “build/bdist.macosx-10.3-fat/egg/_mysql.py”, line 7, in
File “build/bdist.macosx-10.3-fat/egg/_mysql.py”, line 6, in __bootstrap__
ImportError: dynamic module does not define init function (init_mysql)
>>>

Is this due to my omission of the ARCHflags? Any ideas?

By: pilardi

Fri, 16 Oct 2009 15:11:14 +0000

In order to make it work on my system: Snow leopard i386, I had to force python to run in 32 bits mode. So if you want to use 32 bits mysql version, and you are using python > 2.5 you have to force python to use 32 bit architecture, since by default it uses 64 bits. note: osx 10.6 comes with python 2.6 by default.

You can set it system wide by doing in your console:

defaults write com.apple.versioner.python Prefer-32-Bit -bool yes

or just in your session:

export VERSIONER_PYTHON_PREFER_32_BIT=yes

, also I had to force the gcc compiler to use 32 bit architecture when building:

ARCHFLAGS=’-arch i386′

hope it helps someone, it really helped me!

- Pablo