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 exarkun
Recipients Trundle, benjamin.peterson, exarkun, ezio.melotti, georg.brandl, milko.krachounov, ncoghlan
Date 2009-11-17.20:56:55
SpamBayes Score 5.473982e-05
Marked as misclassified No
Message-id <>
How about bringing callable back since there is no obvious replacement
for it?  It's valuable as a LYBL check in circumstances where an object
submitted far away from the place where it's invoked.  Such uses can't
easily be replaced with direct calls to follow the recommended EAFP style.
Date User Action Args
2009-11-17 20:56:57exarkunsetrecipients: + exarkun, georg.brandl, ncoghlan, benjamin.peterson, ezio.melotti, Trundle, milko.krachounov
2009-11-17 20:56:57exarkunsetmessageid: <>
2009-11-17 20:56:55exarkunlinkissue7006 messages
2009-11-17 20:56:55exarkuncreate