Vinay Sajip <[email protected]> added the comment: > 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). ---------- _______________________________________ Python tracker <[email protected]> <http://bugs.python.org/issue11959> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
