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.13:39:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If asyncore and asynchat are (mostly?) supporting an alternate
> socket map, why is it necessary to copy create_socket?
> Shouldn't we be fixing create_socket in asyncore instead?

Well, I don't see how this can be done along with keeping existing behaviour, since if you currently pass a map to the dispatcher constructor, it's not passed to set_socket; fixing it in asyncore would mean changing this fact, and so in theory could break existing code.
Date User Action Args
2012-05-15 13:39:21vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, giampaolo.rodola, r.david.murray, maker
2012-05-15 13:39:21vinay.sajipsetmessageid: <>
2012-05-15 13:39:20vinay.sajiplinkissue11959 messages
2012-05-15 13:39:20vinay.sajipcreate