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 martin.panter
Recipients gvanrossum, martin.panter, vstinner, yselivanov, zwol
Date 2016-03-29.23:09:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459292963.13.0.601193744197.issue26666@psf.upfronthosting.co.za>
In-reply-to
Content
Python’s select() call operates at a minimal OS level. I don’t completely understand your __preselect__() etc proposal, but it does sound like you are trying to invent another higher-level “asynchronous” framework like asyncio.

I think you are wrong about the proxy connection being made in the socksocket() constructor. In general, there could be both write and read events depending on the stage of the proxy connection setup. E.g. with a HTTP proxy, there would be write events to establish the underlying TCP connection, and also to send the CONNECT request, and then a read event to receive the proxy’s response.

Perhaps the SSL socket wrapper objects face a similar situation to your problem. In non-blocking mode, SSLWantRead/WriteError exceptions are raised that indicate which select() event is required.
History
Date User Action Args
2016-03-29 23:09:23martin.pantersetrecipients: + martin.panter, gvanrossum, vstinner, yselivanov, zwol
2016-03-29 23:09:23martin.pantersetmessageid: <1459292963.13.0.601193744197.issue26666@psf.upfronthosting.co.za>
2016-03-29 23:09:23martin.panterlinkissue26666 messages
2016-03-29 23:09:22martin.pantercreate