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 gvanrossum
Recipients asvetlov, gc, gvanrossum, pitrou, vstinner, yselivanov
Date 2015-08-05.17:15:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438794953.86.0.594772950538.issue23749@psf.upfronthosting.co.za>
In-reply-to
Content
Why does the start_tls() function need to know the internal structure of the Transport? I'm hesitant to add this API to Transport; it somehow feels wrong to put such an implementation-specific thing there. E.g. I presume you can't do this for an UDP transport. Or perhaps it could be an API on a subclass of Transport -- then only members of that subclass will support this API.
History
Date User Action Args
2015-08-05 17:15:54gvanrossumsetrecipients: + gvanrossum, pitrou, vstinner, asvetlov, yselivanov, gc
2015-08-05 17:15:53gvanrossumsetmessageid: <1438794953.86.0.594772950538.issue23749@psf.upfronthosting.co.za>
2015-08-05 17:15:53gvanrossumlinkissue23749 messages
2015-08-05 17:15:52gvanrossumcreate