Strange exceptions in MySQLdb

[Hector Villafuerte]

Hi,
I have been using Python 2.3.4 with MySQL 4.0.16-max-nt (through
MySQLdb) for months. Today this messages showed up:

Exception exceptions.AttributeError: "'NoneType' object has no
attribute 'close'" in <bound method Cursor.__del__ of
<MySQLdb.cursors.Cursor instance at 0x0099C148>> ignored
Exception exceptions.AttributeError: "'NoneType' object has no
attribute 'close'" in <bound method Cursor.__del__ of
<MySQLdb.cursors.Cursor instance at 0x009AD080>> ignored
Exception exceptions.AttributeError: "'NoneType' object has no
attribute 'close'" in <bound method Cursor.__del__ of
<MySQLdb.cursors.Cursor instance at 0x009ABF58>> ignored

My scripts work just fine... everything is ok besides this messages
that mean nothing to me
Any suggestions? Thanks in advance!
Hector

 

[Fredrik Lundh]

I have been using Python 2.3.4 with MySQL 4.0.16-max-nt (through
MySQLdb) for months. Today this messages showed up:

Exception exceptions.AttributeError: "'NoneType' object has no
attribute 'close'" in <bound method Cursor.__del__ of
<MySQLdb.cursors.Cursor instance at 0x0099C148>> ignored

this means that the Cursor destructor (the __del__ method) attempts to
call some global object during cleanup, but that object has already been
cleaned away.

for some more information on the cleanup procedure, see:

http://www.python.org/doc/essays/cleanup.html

(this should be mentioned in the reference documentation somewhere,
but I only got through to python.org for long enough to dig up that link)

it's most likely a bug in the MySQLdb driver (objects using destructors
*should* keep references to any object needed by the destructor). to
see if it's really harmless, you may want to check the source code: look
for "close" method calls in the Cursor destructor.

</F>