The Jason Salas Experience

I'm hastily writing a object-oriented GUI app in Python 2.5 that logs keystrokes to a remote textfile. As such, I create Python's file handler object (file/open) in my class's constructor and keep it resident throughout the life of the app to properly handle keypress events. But wanting to be a good memory patron, I'm calling file.close() in the destructor, which technically is after a user could terminate the app by clicking an Exit button I'm handling via sys.exit().

I'm wondering if I might be introducing memory leaks or not managing open objects as well as I could, and possibly introducing dangling references. Consider the following:

def __init__(self):
   self.file = open('foobar.log','a')
def __del__(self):
   self.file.close()
def capture_password(self,event): #handles event logging
   print >> self.file,('Password:%s' % (event.char))
def terminate(self): # handles a 'Quit' button click
   sys.exit()