"Steve Holden" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Thomas Bartkus wrote: > > "Steve Holden" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > > > >>I have a _mysql.c as a part of my distrbution of MySQLdb. Don't you? > >> > > > > > > You made me give that library a good hard stare. > > > > And no - everything is enunciated in clear Python (.py) code with > > corresponding (.pyc) and (.pyo). It appears we have Python source for > > everything. > > > > FWIW: > > > > > >>>>print MySQLdb.version_info > > > > (1, 2, 0, 'final', 1) > > > OK. I saw that my own version was (1, 0, 0, 'final', 1), so I assumed > Andy's updated the package somewhat. However, downloading the source of > 1.2 I see that _mysql.c still appears, and that the package's > __init__.py still includes the line > > include _mysql > > My C:\Python24\Lib\site-packages directory does contain a _mylsql.pyd > file. Would you like to check that we are talking about the same module?
Okay - I neglected to look at the [site-packages] directory itself. Here I do find [_mysql.pyd] full of binary code. A MySQLdb related file that doesn't seem to have a corresponding file with Python source code. Mea culpa! This is on MS Windows [C:\Python23]. But heck! Now I'm looking at the /usr/lib/python2.3/site-packages on a Mandrake Linux box. No [_mysql.] pyd here! Fewer files overall and while there are other file extensions, everything seems to have a corresponding [.py]. print MySQLdb.version_info (0, 9, 2, 'final', 1) Thomas Bartkus -- http://mail.python.org/mailman/listinfo/python-list
