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 vinay.sajip
Recipients giampaolo.rodola, maker, r.david.murray, terry.reedy, vinay.sajip
Date 2012-05-15.16:25:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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?

Sorry I was being a bit dense ... it's been a while since I looked at this. I think you are right that the base create_socket could be changed in this way. I'll work up a patch in my sandbox branch (for easier Rietveld integration).
Date User Action Args
2012-05-15 16:25:31vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, giampaolo.rodola, r.david.murray, maker
2012-05-15 16:25:31vinay.sajipsetmessageid: <>
2012-05-15 16:25:30vinay.sajiplinkissue11959 messages
2012-05-15 16:25:30vinay.sajipcreate