A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108034.html below:

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

[Python-Dev] [Python-checkins] r88395 - python/branches/py3k/Lib/asyncore.py [Python-Dev] [Python-checkins] r88395 - python/branches/py3k/Lib/asyncore.pyexarkun at twistedmatrix.com exarkun at twistedmatrix.com
Sun Feb 13 05:20:59 CET 2011
On 12:34 am, stutzbach at google.com wrote:
>On Sat, Feb 12, 2011 at 4:22 PM, <exarkun at twistedmatrix.com> wrote:
>>Do people want to seriously consider deprecating asyncore and adding a
>>replacement for it to the stdlib?
>
>>(Hey, PyCon is coming up.  How convenient. :)
>
>The desire is there, but it's a hard problem.  There was a similar
>discussion before PyCon 2009, but not much came of it:
>
>http://mail.python.org/pipermail/python-dev/2009-March/086678.html

I started working on a PEP last year, but I didn't get very far partly 
because I doubted the desire.

What part do you think is a hard problem?  Convincing people to switch 
to a new API?  *Defining* the new API doesn't seem very hard to me.

Jean-Paul
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4