Message 160733 - Python tracker

➜

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	giampaolo.rodola, maker, r.david.murray, terry.reedy, vinay.sajip
Date	2012-05-15.14:51:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
But it is create_socket you want to change. So if we add a map argument to that and only pass it to socket if it is non-None, wouldn't that maintain backward compatibility with current asyncore behavior? Neither asyncore nor asynchat calls create_socket, as far as I can see.

But it is create_socket you want to change.  So if we add a map argument to that and only pass it to socket if it is non-None, wouldn't that maintain backward compatibility with current asyncore behavior?  Neither asyncore nor asynchat calls create_socket, as far as I can see.

History
Date	User	Action	Args
2012-05-15 14:51:57	r.david.murray	set	recipients: + r.david.murray, terry.reedy, vinay.sajip, giampaolo.rodola, maker
2012-05-15 14:51:57	r.david.murray	set	messageid: <[email protected]>
2012-05-15 14:51:56	r.david.murray	link	issue11959 messages
2012-05-15 14:51:56	r.david.murray	create