Hi,
I'm trying to checkout a pristine clone from
ssh://h...@hg.python.org/cpython, and it's taking forever:
"""
07:45:35.605941 IP 192.168.0.23.43098 >
virt-7yvsjn.psf.osuosl.org.ssh: Flags [.], ack 22081460, win 14225,
options [nop,nop,TS val 368519 ecr 2401783356], length 0
07:45:38.558348 IP vi
On 8/26/2013 8:51 AM, Antoine Pitrou wrote:
> Le Mon, 26 Aug 2013 08:24:58 -0400,
> Tres Seaver a écrit :
>> On 08/26/2013 04:36 AM, Antoine Pitrou wrote:
>>> event-driven processing using network libraries
>>
>> Maybe I missed something: why should considerations from that topic
>> influence the
Ryan wrote:
Nonblocking sounds too Internet-related. How about...flow?
AsyncParser?
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
Wow, that was quick! I propose that we wait for one more day for any
feedback from others in response to this post, and then accept the PEP.
On Mon, Aug 26, 2013 at 3:19 PM, Victor Stinner wrote:
> 2013/8/26 Guido van Rossum :
> > I have reviewed the PEP and I think it is good. Thank you so much
2013/8/26 Guido van Rossum :
> I have reviewed the PEP and I think it is good. Thank you so much for
> pushing this topic and for your very thorough review of all the feedback,
> related issues and so on. It is an exemplary PEP!
Thanks :-) I updated the PEP:
http://hg.python.org/peps/rev/edd8250f6
Hi Victor,
I have reviewed the PEP and I think it is good. Thank you so much for
pushing this topic and for your very thorough review of all the feedback,
related issues and so on. It is an exemplary PEP!
I've made a bunch of small edits (mostly to improve grammar slightly, hope
you don't mind) a
On Fri, Aug 23, 2013 at 1:30 PM, Charles-François Natali
wrote:
>> About your example: I'm not sure that it is reliable/portable. I sa
>> daemon libraries closing *all* file descriptors and then expecting new
>> file descriptors to become 0, 1 and 2. Your example is different
>> because w is still
Nonblocking sounds too Internet-related. How about...flow?
Ah, I'll probably still end up using Expat regardless.
Eli Bendersky wrote:
>On Mon, Aug 26, 2013 at 10:40 AM, Paul Moore
>wrote:
>
>> On 26 August 2013 17:40, Eli Bendersky wrote:
>>
>>> Yes, exactly :-) "Incremental", though, seems
Paul Moore, 26.08.2013 19:40:
> On 26 August 2013 17:40, Eli Bendersky wrote:
>
>> Yes, exactly :-) "Incremental", though, seems to support the conjecture
>> that it's the input. Which is true, but, since XMLParser is also
>> "incremental" in this sense, slightly confusing.
>
> As a data point, u
On Mon, Aug 26, 2013 at 10:40 AM, Paul Moore wrote:
> On 26 August 2013 17:40, Eli Bendersky wrote:
>
>> Yes, exactly :-) "Incremental", though, seems to support the conjecture
>> that it's the input. Which is true, but, since XMLParser is also
>> "incremental" in this sense, slightly confusing.
How about StreamParser? I mean, even if it isn't quite the same, that name
would still make sense.
Eli Bendersky wrote:
>On Mon, Aug 26, 2013 at 8:57 AM, Antoine Pitrou
>wrote:
>
>> Le Mon, 26 Aug 2013 17:44:41 +0200,
>> Simon Cross a écrit :
>> > On Mon, Aug 26, 2013 at 2:51 PM, Antoine Pitr
On 26 August 2013 17:40, Eli Bendersky wrote:
> Yes, exactly :-) "Incremental", though, seems to support the conjecture
> that it's the input. Which is true, but, since XMLParser is also
> "incremental" in this sense, slightly confusing.
As a data point, until you explained the difference betwe
On Mon, Aug 26, 2013 at 9:21 AM, Antoine Pitrou wrote:
> Le Mon, 26 Aug 2013 09:14:38 -0700,
> Eli Bendersky a écrit :
> >
> > Antoine, you opted out of the tracker issue but I feel it's fair to
> > let you know that after a lot of discussion with Nick and Stefan (*),
> > we've settled on renami
Le Mon, 26 Aug 2013 09:14:38 -0700,
Eli Bendersky a écrit :
>
> Antoine, you opted out of the tracker issue but I feel it's fair to
> let you know that after a lot of discussion with Nick and Stefan (*),
> we've settled on renaming the input methods to feed & close, and the
> output method to rea
On Mon, Aug 26, 2013 at 8:57 AM, Antoine Pitrou wrote:
> Le Mon, 26 Aug 2013 17:44:41 +0200,
> Simon Cross a écrit :
> > On Mon, Aug 26, 2013 at 2:51 PM, Antoine Pitrou
> > wrote:
> > > Because this API is mostly useful when the data is received (*) at a
> > > slow enough speed - which usually
Le Mon, 26 Aug 2013 17:44:41 +0200,
Simon Cross a écrit :
> On Mon, Aug 26, 2013 at 2:51 PM, Antoine Pitrou
> wrote:
> > Because this API is mostly useful when the data is received (*) at a
> > slow enough speed - which usually means from the network, not from a
> > hard drive.
>
> It looks like
On Mon, Aug 26, 2013 at 2:51 PM, Antoine Pitrou wrote:
> Because this API is mostly useful when the data is received (*) at a
> slow enough speed - which usually means from the network, not from a
> hard drive.
It looks like all the events have to be ready before one can start
iterating over .eve
Le Mon, 26 Aug 2013 08:24:58 -0400,
Tres Seaver a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/26/2013 04:36 AM, Antoine Pitrou wrote:
> > event-driven processing using network librarie
>
> Maybe I missed something: why should considerations from that topic
> influence th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/2013 04:36 AM, Antoine Pitrou wrote:
> event-driven processing using network librarie
Maybe I missed something: why should considerations from that topic
influence the design of an API for XML processing? 'feed' and 'close'
make much more s
Le Sat, 24 Aug 2013 14:42:24 -0400,
Terry Reedy a écrit :
> >
> > And these for IncrementalParser:
> >
> > data_received(data)
> > Feed the given bytes data to the incremental parser.
>
> Longer, awkward, and to me ugly in comparison to 'feed'. Since it
> seems to mean more or less
20 matches
Mail list logo
