lvh / async-pep

Draft PEP for asynchronous IO
ISC License
62 stars 7 forks source link

half_close is pretty obscure #7

Open lvh opened 13 years ago

lvh commented 13 years ago

Does it really belong in this PEP?

jerub commented 13 years ago

Lets go with 'no'.

hynek commented 13 years ago

I believe it adds unnecessary complexity/special cases to the initial, supposedly simple PEP.

lvh commented 13 years ago

Okay, taking it out.

glyph commented 12 years ago

I think that you need it, because it's the only way to say "produce some data after EOF", which is critical for a subprocess-based transport.