[Python-ideas] Tulip / PEP 3156 (original) (raw)
[Python-ideas] Tulip / PEP 3156 - subprocess events
Greg Ewing greg.ewing at canterbury.ac.nz
Tue Jan 22 05:17:57 CET 2013
- Previous message: [Python-ideas] Tulip / PEP 3156 - subprocess events
- Next message: [Python-ideas] Tulip / PEP 3156 - subprocess events
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Glyph wrote:
this means that the protocol will immediately begin interacting with the transport in this vague, undefined, not quite connected state,
You still haven't explained why the protocol can't simply refrain from doing anything with the transport until its connection_made() is called.
If a transport is always to be assumed ready-to-go as soon as it's exposed to the outside world, what is the point of having connection_made() at all?
-- Greg
- Previous message: [Python-ideas] Tulip / PEP 3156 - subprocess events
- Next message: [Python-ideas] Tulip / PEP 3156 - subprocess events
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]