On Jul 14, 2011, at 4:05 AM, Laurens Van Houtven wrote:
> At least in Twisted, transports and protocols do not exist in a vacuum;
> they have to be hooked up via the reactor. Will this PEP define
> a (skeletal) API to be implemented by potential reactors, or is that
> going to left entirely unspe
On Jul 14, 2011, at 2:48 AM, Tim Allen wrote:
> On Wed, Jul 13, 2011 at 02:03:03PM +0200, Laurens Van Houtven wrote:
>> So, some of you might remember my async-pep post a while ago. Some people
>> correctly complained there was no code or text. There's some code and quite
>> a bit of text now. In
On 10:26 am, screwt...@froup.com wrote:
>On Thu, Jul 14, 2011 at 07:05:38PM +1000, Tim Allen wrote:
>>- You might also want to create an optional Transport method to wrap
>>the
>> sendfile(2) and/or splice(2) functions.
>
>I suggested this not knowing whether Python would ever grow support for
>
On Thu, Jul 14, 2011 at 07:05:38PM +1000, Tim Allen wrote:
> - You might also want to create an optional Transport method to wrap the
> sendfile(2) and/or splice(2) functions.
I suggested this not knowing whether Python would ever grow support for
sendfile(), since it seemed like the sort of thi
On Thu, Jul 14, 2011 at 10:05:00AM +0200, Laurens Van Houtven wrote:
> On Thu, Jul 14, 2011 at 8:48 AM, Tim Allen wrote:
> > The idea of Protocols implementing Transports is vaguely gestured at as
> > a Useful Thing, but not much detail is given. I think it would be useful
> > for the final PEP to
On Thu, Jul 14, 2011 at 8:48 AM, Tim Allen wrote:
> On Wed, Jul 13, 2011 at 02:03:03PM +0200, Laurens Van Houtven wrote:
> > So, some of you might remember my async-pep post a while ago. Some people
> > correctly complained there was no code or text. There's some code and
> quite
> > a bit of tex
On Wed, Jul 13, 2011 at 02:03:03PM +0200, Laurens Van Houtven wrote:
> So, some of you might remember my async-pep post a while ago. Some people
> correctly complained there was no code or text. There's some code and quite
> a bit of text now. In fact, it even has a PEP number (3153)! So I'm
> soli
Hey!
So, some of you might remember my async-pep post a while ago. Some people
correctly complained there was no code or text. There's some code and quite
a bit of text now. In fact, it even has a PEP number (3153)! So I'm
soliciting feedback again.
There's an issue tracker that ideally describe
