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 r.david.murray
Recipients facundobatista, italip, jjlee, ncoghlan, orsenthil, r.david.murray, sidnei
Date 2013-07-29.01:40:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, this is a very good point.  (And your passing test is worthwhile, you are correct.)  

People are expected to be able to write handlers, so clearly the timeout API needs to be documented, if for no other reason than to keep a handler writer from stomping on the timeout attribute inappropriately.  

But there is a code smell to this "API", and I wonder if it is worth someone taking time to think it all through again to see if there is a better way to do it :(
Date User Action Args
2013-07-29 01:40:54r.david.murraysetrecipients: + r.david.murray, facundobatista, jjlee, ncoghlan, orsenthil, sidnei, italip
2013-07-29 01:40:54r.david.murraysetmessageid: <>
2013-07-29 01:40:54r.david.murraylinkissue4079 messages
2013-07-29 01:40:53r.david.murraycreate