Comments on: MySQLdb on Leopard

By: hillscottc

hillscottc — Mon, 11 Jan 2010 05:47:19 +0000

I am also totally frustrated with
ImportError: dynamic module does not define init function (init_mysql)

@ssteinerX , I see you got it fixed, but what you actually did isn’t clear to me. I also don’t want to ‘downgrade’ to 32 bit. Can you please explain “just install the one with the right architecture” ?

By: ssteinerX

ssteinerX — Thu, 31 Dec 2009 14:45:12 +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: muanis

muanis — Sat, 13 Jun 2009 23:56:40 +0000

I’ve got the same problem.

Running mysql 5.1.35. After discovering that I should change to 32 bit version, repeated all the steps and got the same error about the init function.

>>> import MySQLdb
import sys, pkg_resources, imp
Traceback (most recent call last):
File “”, line 1, in
File “MySQLdb/__init__.py”, line 19, in
import _mysql
File “build/bdist.macosx-10.5-i386/egg/_mysql.py”, line 7, in
File “build/bdist.macosx-10.5-i386/egg/_mysql.py”, line 6, in __bootstrap__
ImportError: dynamic module does not define init function (init_mysql)

After a couple of hours debugging I noticed that the dist and build dirs of MySQLdb 1.2.2 were not removed when I issue a python setup.py clean.

I manually removed both of them and got everything working fine.

By: Kévin Dunglas

Kévin Dunglas — Fri, 24 Apr 2009 11:09:02 +0000

Your link to download MySQL 5.0.41 is dead.
You can get the tarball from http://downloads.mysql.com/archives.php?p=mysql-5.0&v=5.0.41

By: Paul B. Hartzog

Paul B. Hartzog — Thu, 23 Apr 2009 06:29:44 +0000

http://www.newtonslore.com/2007/06/09/mysqldb-lays-an-egg/

will get you through the egg errors

By: pvc

pvc — Tue, 27 Jan 2009 00:05:30 +0000

The _mysql.so ImportError on init_mysql puzzeled my for a while until I discovered that “python setup.py clean” does not do a complete job of discarding the prior build. If you previously built against a 64 bit library of mysql you need to manually delete everything below the build directory before doing a new build with the 32 bit version.

By: Install Python MySQL db module? | keyongtech

Install Python MySQL db module? | keyongtech — Sun, 18 Jan 2009 16:40:22 +0000

[...] -Conrad I tried this a couple of weeks ago using macports and had problems. See, for example: http://www.davidcramer.net/code/57/m…n-leopard.html I read about several people who went in and edited the source files to work out the bugs on [...]

By: How to finally fix that damned MySQLdb module on Leopard « Nerd Stuff

How to finally fix that damned MySQLdb module on Leopard « Nerd Stuff — Sun, 18 Jan 2009 10:50:54 +0000

[...] David Cramer.net – MySQLdb on Leopard [...]

By: indiehead

indiehead — Tue, 30 Dec 2008 02:01:14 +0000

Great work, unfortunately didn’t work this end, any ideas?

indiehead:MySQL-python-1.2.2 indiehead$ sudo python setup.py install
running install
running bdist_egg
running egg_info
writing MySQL_python.egg-info/PKG-INFO
writing top-level names to MySQL_python.egg-info/top_level.txt
writing dependency_links to MySQL_python.egg-info/dependency_links.txt
reading manifest file ‘MySQL_python.egg-info/SOURCES.txt’
reading manifest template ‘MANIFEST.in’
writing manifest file ‘MySQL_python.egg-info/SOURCES.txt’
installing library code to build/bdist.macosx-10.5-i386/egg
running install_lib
running build_py
copying MySQLdb/release.py -> build/lib.macosx-10.5-i386-2.5/MySQLdb
running build_ext
building ‘_mysql’ extension
creating build/temp.macosx-10.5-i386-2.5
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -pipe -Dversion_info=(1,2,2,’final’,0) -D__version__=1.2.2 -I/usr/local/mysql/include -I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c _mysql.c -o build/temp.macosx-10.5-i386-2.5/_mysql.o -g -Os -arch i386 -fno-common -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -DIGNORE_SIGHUP_SIGQUIT
_mysql.c:37: error: syntax error before ‘uint’
_mysql.c:38: error: syntax error before ‘unsigned’
In file included from /usr/local/mysql/include/mysql.h:47,
from _mysql.c:40:
/usr/include/sys/types.h:84: error: syntax error before ‘typedef’
_mysql.c:485:3: error: invalid preprocessing directive #uint
_mysql.c:486:3: error: invalid preprocessing directive #uint
error: command ‘gcc’ failed with exit status 1

By: Emily

Emily — Mon, 10 Nov 2008 22:08:43 +0000

I'm having the same ImportError problem as well, but I've checked that mysql, python, and _mysql.so in the MySQLdb egg are all 32-bit. Everything I've found googling this problem has indicated the same solution that's been suggested here: that the architectures don't match. Any other suggestions or anything else that might be 64-bit and causing the problem?