[Zope] sorry, repost of can't get MysqL working with zope, help me please

[Jens Vagelpohl]

you need to do something like "make clean" first or manually delete all .o 
and .so files within the MySQLDB directories.

jens

P.S.: please keep this on the mailing list so that other people can 
benefit from it, too.

On Monday, November 12, 2001, at 09:32 , Jacob Singh wrote:

> This is the scenario, when trying to re-run the setup script for
> MySQLDB:
> And this is running from the correct python version.  I even deleted all
> the files (that I know of ) from the python dir that pertained to
> MySQLDB
>
> [org@server1 MySQL-python-0.9.0]$ python setup.py build
> running build
> running build_py
> not copying CompatMysqldb.py (output up-to-date)
> not copying _mysql_exceptions.py (output up-to-date)
> not copying MySQLdb/__init__.py (output up-to-date)
> not copying MySQLdb/converters.py (output up-to-date)
> not copying MySQLdb/connections.py (output up-to-date)
> not copying MySQLdb/cursors.py (output up-to-date)
> not copying MySQLdb/sets.py (output up-to-date)
> not copying MySQLdb/times.py (output up-to-date)
> not copying MySQLdb/constants/__init__.py (output up-to-date)
> not copying MySQLdb/constants/CR.py (output up-to-date)
> not copying MySQLdb/constants/FIELD_TYPE.py (output up-to-date)
> not copying MySQLdb/constants/ER.py (output up-to-date)
> not copying MySQLdb/constants/FLAG.py (output up-to-date)
> not copying MySQLdb/constants/REFRESH.py (output up-to-date)
> not copying MySQLdb/constants/CLIENT.py (output up-to-date)
> running build_ext
> skipping '_mysql' extension (up-to-date)
> [org@server1 MySQL-python-0.9.0]$
>
>
> -----Original Message-----
> From: Jens Vagelpohl [mailto:jens@zope.com]
> Sent: Monday, November 12, 2001 7:59 AM
> To: Jacob Singh
> Cc: zope@zope.org
> Subject: Re: [Zope] sorry, repost of can't get MysqL working with zope,
> help me please
>
> to get rid of that error message you must recompile the Python-MySQLDB
> using your newer python.
>
> different versions of python have no problem at all co-existing
> peacefully,
>   as long as you don't install them in the very same location as the old
>
> version. simply overwriting an existing installation, however, will give
>
> you problems along the way.
>
> jens
>
>
> On Sunday, November 11, 2001, at 05:48 , Jacob Singh wrote:
>
>> So here is what I have tried:
>>
>>
>>
>> I installed the Python-MySQLDB mod, but was using an old version of
>> python, then I upgraded python and re-installed it.  then I banged my
>> head against the wall trying to figure out how to use my python
>> executable and not Zope's.  Finnally figured that out (basically
>> undocumented) So then ZMySQLdb showed up as functional but gave the
>> following message and restarted the server whenever I tried to use it:
>>
>>
>>
>> WARNING: Python C API version mismatch for module _mysql:
>>
>>   This Python has API version 1010, module _mysql has version 1007.
>>
>>
>>
>> I have no idea what this means, so I tried making a symlink between a
>> directory in my lib/python and lib/python2.1 directories to the
>> directory containing the Python-MySQLdb .so file and using the Zope
>> provided interpreter (to no avail).  It can't find the module.  I
> think
>> one of my problems may also lie in that I don't know how to uninstall
>> the old python, I didn't really upgrade, I just installed the new one
>> and overwrote the python executable, with the new one, I know this
>> probably wasn't too smooth, but this is a learning process.  NEway,
> any
>> help would be GREATLY appreciated.  And if any Zope Dev's are reading
>> this. PLEASE make MySQL and PostGRES connectivity standard with any
> Zope
>> installation.
>>
>> Thank you
>>
>> Jacob Singh
>>
>
>