Django + MySQL on Mac OS 10.6.2 Snow Leopard

I have ultimately solved my own problem, with of course, the subconscious and conscious help from the many posts, blogs, and mail logs I’ve read. I would give links if I could remember.

In a nutshell, I reinstalled EVERYTHING using MacPorts.

After editing ~/.bash_profile and commenting out all the previous modifications to ${PATH}, I downloaded the dmg for Snow Leopard and ran through its installation.

Then opened the terminal and ran the self update.

sudo port selfupdate
sudo port install python26

That second part, installing Python 2.6, took forever. But when it completed it prompted me with the following:

To fully complete your installation and make python 2.6 the default, please run

sudo port install python_select  
sudo python_select python26

I did both and they went quick.

I forgot to mention how handy ‘port search ‘ command is. I searched for ‘mysql’ and similar to find the thing to type after ‘install’. But I proceeded with reinstalling both the client and server for MySQL. Perhaps I did this in reverse order, but the end result worked fine.

sudo port install mysql5
...
--->  Installing mysql5 @5.1.41_0
The MySQL client has been installed.
If you also want a MySQL server, install the mysql5-server port.

So naturally:

sudo port install mysql5-server

I love how the so many of the macports installations give you feedback as to what to do next. At the end of the server installation, it said the following:

******************************************************
* In order to setup the database, you might want to run
* sudo -u _mysql mysql_install_db5
* if this is a new install
******************************************************

It was a new install for me (didn’t have any local schemas). For completeness, and for my own reference, here is the output of running that command:

Installing MySQL system tables...
OK
Filling help tables...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:

/opt/local/lib/mysql5/bin/mysqladmin -u root password 'new-password'
/opt/local/lib/mysql5/bin/mysqladmin -u root -h iMac.local password 'new-password'

Alternatively you can run:
/opt/local/lib/mysql5/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:
cd /opt/local ; /opt/local/lib/mysql5/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd /opt/local/mysql-test ; perl mysql-test-run.pl

Please report any problems with the /opt/local/lib/mysql5/bin/mysqlbug script!

The latest information about MySQL is available at http://www.mysql.com/
Support MySQL by buying support/licenses from http://shop.mysql.com/

Almost done. Earlier in my ‘port search’ing I came across this interesting port:

py26-mysql @1.2.2 (python, devel, databases)
Python interface to mysql

With much, much hope that this would provide me with MySQLdb package, I installed it (and it did).

sudo port install py26-mysql

Afterwords I cranked up the python interpreter attempted to import MySQLdb, the very thing in my way all this time.

iMac:~ drhoden$ python
Python 2.6.4 (r264:75706, Dec 15 2009, 18:00:14) 
[GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import MySQLdb
/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated from sets import ImmutableSet
>>> 

A warning, but It worked!!

Just one more thing:

sudo port install py26-django

After all of this I was finally able to crank up my Django project and remotely connect to my company’s MySQL server!! It may not have been necessary to reinstall Django using MacPorts, but I wasn’t going to risk complications.

Leave a Comment