On Tue, Sep 8, 2009 at 19:56, Benjamin Peterson <benjamin@python.org> wrote:

2009/9/7 Eric Pruitt <eric.pruitt@gmail.com>:

...

Hello all,

I have been working on adding asynchronous I/O to the Python subprocess module as part of my Google Summer of Code project. Now that I have finished documenting and pruning the code, I present PEP 3145 for its inclusion into the Python core code. Any and all feedback on the PEP (http://www.python.org/dev/peps/pep-3145/) is appreciated.

Hi Eric, One of the reasons you're not getting many response is that you've not pasted the contents of the PEP in this message. That makes it really easy for people to comment on various sections.

BTW, it seems like you were trying to use reST formatting with the text PEP layout. Double backquotes only mean something in reST.

That reST markup is my fault, not Eric. So used to reST PEPs that I just instinctively added it when I check the PEP in. -Brett

On Tue, Sep 8, 2009 at 19:56, Benjamin Peterson <benjamin@python.org> wrote:

2009/9/7 Eric Pruitt <eric.pruitt@gmail.com>:

...

Hello all,

I have been working on adding asynchronous I/O to the Python subprocess module as part of my Google Summer of Code project. Now that I have finished documenting and pruning the code, I present PEP 3145 for its inclusion into the Python core code. Any and all feedback on the PEP (http://www.python.org/dev/peps/pep-3145/) is appreciated.

Hi Eric, One of the reasons you're not getting many response is that you've not pasted the contents of the PEP in this message. That makes it really easy for people to comment on various sections.

BTW, it seems like you were trying to use reST formatting with the text PEP layout. Double backquotes only mean something in reST.

That reST markup is my fault, not Eric. So used to reST PEPs that I just instinctively added it when I check the PEP in. -Brett