MySQLdb - possible without install?

Ken ken_chiba at
Thu Jul 12 06:26:22 EDT 2001

I'm no expert with this at all... could I get some pointers?  I'm
assuming that you're saying that I need to compile MySQLdb with the
MySQL and Python versions that my provider uses.  This will result in
the creation of a MySQLdb directory in the site-packages directory of
Python.  Does it produce anything else?

After this is created, do I just copy that directory (MySQLdb) to a
MySQLdb directory on the provider side (in this case.. within
cgi-bin)?  And finally, what line can I put within my scripts to pull
this information in? (ie.:  import ??)

How can this keep track of what directory MySQL and Python are in? (or
are there configuration files that I can change - AFTER the compile?)

Thanks for your help,


On Thu, 12 Jul 2001 11:55:50 +0200, gerhard.nospam at (Gerhard
=?iso-8859-1?Q?H=E4ring?=) wrote:

>On Thu, 12 Jul 2001 02:44:29 GMT, Ken <ken_chiba at> wrote:
>>Just curious.  I'm with an ISP that allows running of scripts, and has
>>MySQL database access.  They have a perl API installed, but nothing to
>>support Python.  I was wondering if it was possible to just copy over
>>the MySQLdb directory from the site-packages area of Python, and just
>>"import" it into the scripts?
>Yes, this works. MySQLdb needs a compiled extension module, however. You'll
>need a compiled version for the platform your provider uses.
>mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
>web:              public key at homepage
>public key fingerprint: DEC1 1D02 5743 1159 CD20  A4B6 7B22 6575 86AB 43C0
>reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))

More information about the Python-list mailing list