Yury Selivanov added the comment:
I guess PEP 3156 covers this, closing this one.
--
nosy: +yselivanov
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7
David Beazley d...@dabeaz.com added the comment:
Anyone contemplating the use of aio_ functions should first go read The Story
of Mel.
http://www.catb.org/jargon/html/story-of-mel.html
--
nosy: +dabeaz
___
Python tracker rep...@bugs.python.org
Jesús Cea Avión j...@jcea.es added the comment:
Thanks, David, for the link. The story is really touching :-).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7
___
David Beazley d...@dabeaz.com added the comment:
Glad you liked it! I think there is a bit of a cautionary tale in there
though. With aio_, there is the promise of better performance, but you're also
going to need a *LOT* of advance planning and thought to avoid creating a
tangled coding
New submission from Jesús Cea Avión j...@jcea.es:
This issue is a placeholder for exposing Async IO thru Python.
The relevant mail thread is at:
http://mail.python.org/pipermail/python-dev/2010-October/104770.html
Relevant resources:
Changes by Brian Curtin cur...@acm.org:
--
nosy: +brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7
___
___
Python-bugs-list
Antoine Pitrou pit...@free.fr added the comment:
From the python-dev thread:
http://mail.python.org/pipermail/python-dev/2010-October/104782.html
“os._exit is useful. os.open is useful. aio_* are *not* useful. For anything.
If there's anything you think you want to use them for, you're wrong.
Changes by Giampaolo Rodola' g.rod...@gmail.com:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7
___
___
