This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients brian.curtin, jcea, pitrou
Date 2011-02-04.15:41:31
SpamBayes Score 1.3840474e-07
Marked as misclassified No
Message-id <>
From the python-dev thread:

“os._exit is useful. is useful. aio_* are *not* useful. For anything. If there's anything you think you want to use them for, you're wrong. It either won't work properly or it will worse performing than the simpler alternatives.”

“I'd like to echo this sentiment.  This is not about providing a 'safe' wrapper to hide some powerful feature of these APIs: the POSIX aio_* functions are really completely useless.


Not only is the performance usually worse than expected, the behavior of aio_* functions require all kinds of subtle and mysterious coordination with signal handling, which I'm not entirely sure Python would even be able to pull off without some modifications to the signal module.  (And, as Jean-Paul mentioned, if your OS kernel runs out of space in a queue somewhere, completion notifications might just never be delivered at all.)”
Date User Action Args
2011-02-04 15:41:32pitrousetrecipients: + pitrou, jcea, brian.curtin
2011-02-04 15:41:32pitrousetmessageid: <>
2011-02-04 15:41:31pitroulinkissue11117 messages
2011-02-04 15:41:31pitroucreate