Message160727
| 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 |
<1337089161.28.0.626535787585.issue11959@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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. |
|