I am going further, and to test some .py code in my machine I had to add mysqldb. Then, opening it, he refused to work unless ‘easy install‘ was installed too. They must have been friend. He tried to get his mate by himself and didn’t suceed. So there I was, searching the net to get the second package. That was a .egg file. Now .egg file are in general archives. Not this. I actually had to call “sh thefileIjustdownloaded”. Something that I happen to discover in some obscure page. Now with the easy install installed, I could go one step further to install mysqldb. The next step was discovering that he was not willing to let me install mysqldb unless I had a version of mysql running in loco. How patient am I! In any case I wanted to have a local mysql, so there I was looking for the right version. Firsl locate mysql.com, then proceed over the terrorist notice: “unless you are a god in programming buy a local guide”. Now what kind of Mac have I got? I know it is not Intel, so it is PowerPc. 32 or 64? Google doesn’t help. Wikipedia neither, andthe About this Mac is similarly obscure. I just know that my cpu is PowerPC G4 (1.1). No reference to 32-bit or 64-bit. It is probably a question too stupid to ask? Let’s try. I download the 64. Install. Run from the System Preferences. It does not start. But he did not protest when I installed it, it MUST be the right type… right? I actually need to add a few things in the PATH. Look he does not even find the mysql. But here they are. Let’s try to run it, you know just for sport.
>WRONG CPU TYPE.
Hmm, looks like I have a 32 bit. Let’s download the 32 bit. Read Me: unfortunately installing a new version of mysql does not disinstall the previous… Great! So google: how do I unistall a mysql that was wrongly installed (although-I-can’t-understand why-I had to instal-it-in-the-firstplace-since-I-only-wanted-to-connect-to-the-far-away-server). Answer. Worked fine. Except that in the meantime I had alread installed half of the 32 bit version. Let’s delete all and start again. Ok, installed. Now let’s go back to mysqldb.
Same problem, he cannot find “mysql_config”. I use spotlight, I can’t find it either. I use quicksilver (they promised me that it was the best), … not in this. I use google. Only one person had the same problem (and is mirrored all over the place), but the suggestion don’t seem to apply.
Someone suggests: you need to tell the setup where to find mysql_config. Well, how can I tell him if I don’t find it myself. It continues: normally is in …/mysql/bin/
“normally” works fine for me. So I found it, how do I tell him? The error was raised by setup_posix.py. Here you go:
f = popen(”%s –%s” % (mysql_config.path, what))
and no way is mysql_config.path defined. I change it into:
f = popen(”%s –%s” % (’/usr/local/mysql/bin/mysql_config’, what))
and it works!
python setup.py install
sudo python setup.py install
A long list of things that happened, and it ends with something similar to:
mysqldb installed with easy install.
“…with easy install”: fuck off!
There must be a better way to pass the sunday. In any case now that mysqldb is installed I just discovered I cannot run the code because he cannot connect to the mysql. It must be because of the university proxy. It doesn’t matter, I shall use test it directly on the net.