This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients ncoghlan, vinay.sajip
Date 2012-09-18.14:49:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm not against making this change, but I'm curious - why would a handler do clean-up I/O in its release() method (which is just for releasing the I/O lock) where it could just as easily override the close() method to do the same thing? It seems like programmer error to be doing any I/O in a handler after close() is called on it.
Date User Action Args
2012-09-18 14:49:31vinay.sajipsetrecipients: + vinay.sajip, ncoghlan
2012-09-18 14:49:31vinay.sajipsetmessageid: <>
2012-09-18 14:49:31vinay.sajiplinkissue15960 messages
2012-09-18 14:49:30vinay.sajipcreate