Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11959> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
