Re: Standard Asynchronous Python

2012-09-15 Thread Bryan
Dustin J. Mitchell wrote: > Thanks for the second round of responses.  I think this gives me some > focus - concentrate on the API, talk to the framework developers, and > start redrafting the PEP sooner rather than later. That's mostly what you came in with, but talking to the framework developer

Re: Standard Asynchronous Python

2012-09-11 Thread Dustin J. Mitchell
Thanks for the second round of responses. I think this gives me some focus - concentrate on the API, talk to the framework developers, and start redrafting the PEP sooner rather than later. Thanks! Dustin -- http://mail.python.org/mailman/listinfo/python-list

Re: Standard Asynchronous Python

2012-09-10 Thread Terry Reedy
On 9/10/2012 7:36 AM, Dustin J. Mitchell wrote: The responses have certainly highlighted some errors in emphasis in my approach. * My idea is to propose a design PEP. (Steven, Dennis) I'm not at *all* suggesting including uthreads in the standard library. It's a toy implementation I used to dev

Re: Standard Asynchronous Python

2012-09-10 Thread Oscar Benjamin
On 2012-09-10, Dennis Lee Bieber wrote: > On Sun, 9 Sep 2012 20:07:51 -0400, "Dustin J. Mitchell" > declaimed the following in > gmane.comp.python.general: > >> >> My proposal met with near-silence, and I didn't pursue it. Instead, I >> did what any self-respecting hacker would do - I wrote up a

Re: Standard Asynchronous Python

2012-09-10 Thread Steven D'Aprano
On Mon, 10 Sep 2012 07:36:11 -0400, Dustin J. Mitchell wrote: > The responses have certainly highlighted some errors in emphasis in my > approach. > > * My idea is to propose a design PEP. (Steven, Dennis) I'm not at *all* > suggesting including uthreads in the standard library. It's a toy > imp

Re: Standard Asynchronous Python

2012-09-10 Thread Dustin J. Mitchell
The responses have certainly highlighted some errors in emphasis in my approach. * My idea is to propose a design PEP. (Steven, Dennis) I'm not at *all* suggesting including uthreads in the standard library. It's a toy implementation I used to develop my ideas. I think of this as a much smaller

Re: Standard Asynchronous Python

2012-09-09 Thread Bryan
Dustin J. Mitchell wrote: > After seeing David Mertz's talk at PyCon 2012, "Coroutines, event > loops, and the history of Python generators" [1], I got thinking again > about Python's expressive power for asynchronous programming. I lament the confusion of generators and coroutines. Generators are

Re: Standard Asynchronous Python

2012-09-09 Thread Steven D'Aprano
On Sun, 09 Sep 2012 20:07:51 -0400, Dustin J. Mitchell wrote: > After seeing David Mertz's talk at PyCon 2012, "Coroutines, event loops, > and the history of Python generators" [1], I got thinking again about > Python's expressive power for asynchronous programming. [...] > I'm considering re-draf

Standard Asynchronous Python

2012-09-09 Thread Dustin J. Mitchell
After seeing David Mertz's talk at PyCon 2012, "Coroutines, event loops, and the history of Python generators" [1], I got thinking again about Python's expressive power for asynchronous programming. Generators, particularly with the addition of 'yield from' and 'return' in PEP 380 [2], allow us to