On Sun, 13 Feb 2011 19:18:52 +1000 Nick Coghlan <ncogh...@gmail.com> wrote: > > If there is an essential subset of the API that the Twisted devs think > would be a suitable replacement for asyncore, while providing a more > straightforward migration path into Twisted itself, then it certainly > makes sense to include it.
That subset would be the reactor (actually, the various reactor implementations) and its close dependencies. However, that might already amount to a sizeable chunk of code :-) (for good reason, of course: even Twisted Core does much, much more than asyncore). > The other possible sticking point I can see is that I don't know how > Twisted's licensing works - is there anyone with the legal authority > to appropriately license the code to the PSF for inclusion in the > standard library? Twisted's license is MIT-like so I don't think there would be any so-called "licensing" problem. :-) Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
