[Python-Dev] [Python-checkins] r88395 - python/branches/py3k/Lib/asyncore.py

[Daniel Stutzbach]

On Sat, Feb 12, 2011 at 8:20 PM, <exarkun at twistedmatrix.com> wrote:

> What part do you think is a hard problem?  Convincing people to switch to a
> new API?
>

I think the hard parts is coming up with an API that's simple enough to
learn quickly but powerful enough for to cover most use-cases and cleanly
extendable to cover use-cases we haven't thought of.

If we go with something based on or inspired by Twisted, that solves some
problems, but creates others.  Will users be able to later migrate to using
Twisted proper?  Will the standard library module and Twisted go out of
sync?  What happens if a user tries to use both the standard library module
and Twisted?

Please understand that I'm not saying these are insurmountable problems.
 I'm just suggesting things that might be good to address in a PEP.


> *Defining* the new API doesn't seem very hard to me.
>

If you have the skills and experience so that designing a async API is not
as hard for you, please run with it.  :-)  Personally, I would love to see
asyncore deprecated in favor of something better.

-- 
Daniel Stutzbach
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110214/f74a2071/attachment.html>