[Python-ideas] [Python-Dev] Python needs a standard asynchronous return object (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Sep 21 15:40:28 CEST 2010
- Previous message: [Python-ideas] [Python-Dev] Python needs a standard asynchronous return object
- Next message: [Python-ideas] Python needs a standard asynchronous return object
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Sep 21, 2010 at 11:25 PM, Jesse Noller <jnoller at gmail.com> wrote:
There has been discussion, off and on for years about doing including a stripped down deferred object; and yet no one has stepped up to *do it*, so it might be hilariously easy, it might be a 40 line module, but it doesn't matter if no one steps up to do the pep, and commit the code, and commit to maintaining it.
Indeed. Thread and process pools had similarly been talked about for quite some time before Brian stepped up to actually do the work of writing and championing PEP 3148.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-ideas] [Python-Dev] Python needs a standard asynchronous return object
- Next message: [Python-ideas] Python needs a standard asynchronous return object
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]