On 15 February 2011 00:45, <exar...@twistedmatrix.com> wrote: > As far as the difficulties of "finding" the good ideas in Twisted goes, > there are several people familiar with Twisted already contributing to this > thread. Between us all, I'm sure we can dig out the insidiously buried > secrets. As I mentioned before, I've also started a PEP myself to lay bare > the mysteries. I may try working on it some more, since there seems to be > some interest.
FWIW, I am +1 on seeing a PEP for a twisted-based async framework. Probably targeted at 3.3, that should be plenty of time. I'd like it to be upward compatible with Twisted proper. If I'm expanding the scope of my code anywhere, it will be to full twisted, and I'd rather not have to rewrite what's already there. I've no reason to criticise any of the other async frameworks out there, but it seems clear to me that Twisted is well established as the "best of breed" in this area. The PEP should address what will happen with the dependency on zope.interface. Getting interfaces into the stdlib has *also* been discussed often in the past, and has never happened. It might even be contentious enough to warrant a second sub-PEP covering just that area. While I'm sure there's still plenty of technical issues we can cover in this thread, I think that a PEP would focus discussion a lot more clearly. Paul. _______________________________________________ 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
