Author r.david.murray
Recipients docs@python, fviard, r.david.murray, terry.reedy
Date 2013-10-08.15:51:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381247519.78.0.433848459234.issue19154@psf.upfronthosting.co.za>
In-reply-to
Content
It seems to me that there is indeed an issue of some sort here, but its locus is (to me) unclear.  I haven't commented before this because I wanted to read the docs...but I haven't had time yet :)  

One question is, is it even expected that passing a Request to select will work?  If it *is* expected, then what is the API that req should be conforming to?  This API may be an implicit one that is not documented, or perhaps it is documented in select (I haven't checked).  If req is conforming to the explicit or implicit API, then the bug would be in select.  Otherwise it is in httplib.

Or, if this isn't something we've been supporting in the past, then as Terry says it is a new feature.
History
Date User Action Args
2013-10-08 15:51:59r.david.murraysetrecipients: + r.david.murray, terry.reedy, docs@python, fviard
2013-10-08 15:51:59r.david.murraysetmessageid: <1381247519.78.0.433848459234.issue19154@psf.upfronthosting.co.za>
2013-10-08 15:51:59r.david.murraylinkissue19154 messages
2013-10-08 15:51:59r.david.murraycreate