Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Adam Olsen
On Dec 11, 2007 11:00 PM, Andrew Bennetts <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > On Dec 11, 2007 4:54 PM, Jan Claeys <[EMAIL PROTECTED]> wrote: > > > Op vrijdag 07-12-2007 om 07:26 uur [tijdzone -0700], schreef Sean > > > Reifschneider: > > > > I would say that this is an optimiza

Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Andrew Bennetts
Guido van Rossum wrote: > On Dec 11, 2007 4:54 PM, Jan Claeys <[EMAIL PROTECTED]> wrote: > > Op vrijdag 07-12-2007 om 07:26 uur [tijdzone -0700], schreef Sean > > Reifschneider: > > > I would say that this is an optimization that helps a specific set of > > > platforms, including one that I think w

Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Guido van Rossum
On Dec 11, 2007 6:01 PM, Greg Ewing <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > > On Dec 11, 2007 4:54 PM, Jan Claeys <[EMAIL PROTECTED]> wrote: > > > >>Almost every laptop user would benefit from it, and even some desktop or > >>server users might save on their electric power bill...

Re: [Python-Dev] sliceobject Py_None step inquiry

2007-12-11 Thread Calvin Spealman
I think that should not change. None is different than 0. It makes sense to use it as a "use the default value" kind of place holder. Silently using 1 when you pass 0 is a very different thing. Maybe the slice was calculated and the developer should know about it being 0, because in this cas

[Python-Dev] sliceobject Py_None step inquiry

2007-12-11 Thread Joseph Armbruster
I was playing around with sliceobject.c this evening and noticed the following behavior. If you slice with a step 0, you receive a ValueError but when you slice with a step of None, the step is set to 1. As an example, observe the following interactive session: >>> a = [1,2,3,4,5,6] >>> b

Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Greg Ewing
Guido van Rossum wrote: > On Dec 11, 2007 4:54 PM, Jan Claeys <[EMAIL PROTECTED]> wrote: > >>Almost every laptop user would benefit from it, and even some desktop or >>server users might save on their electric power bill... > > > Do you have data to support this claim? Even if it doesn't save

Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Guido van Rossum
On Dec 11, 2007 4:54 PM, Jan Claeys <[EMAIL PROTECTED]> wrote: > Op vrijdag 07-12-2007 om 07:26 uur [tijdzone -0700], schreef Sean > Reifschneider: > > I would say that this is an optimization that helps a specific set of > > platforms, including one that I think we really care about, the OLPC > >

Re: [Python-Dev] Signals+Threads (PyGTK waking up 10x/sec).

2007-12-11 Thread Jan Claeys
Op vrijdag 07-12-2007 om 07:26 uur [tijdzone -0700], schreef Sean Reifschneider: > I would say that this is an optimization that helps a specific set of > platforms, including one that I think we really care about, the OLPC > which needs it for decreased battery use. Almost every laptop user would

Re: [Python-Dev] builtin_format function code-spacing in bltinmodule.c

2007-12-11 Thread Guido van Rossum
It is important; care to submit a fix? On Dec 11, 2007 11:08 AM, Joseph Armbruster <[EMAIL PROTECTED]> wrote: > All, > > Not sure if this is significant or not but the spacing of the builtin_format > function is not consistent with the > rest of the bltinmodule.c file. -- --Guido van Rossum (hom

[Python-Dev] builtin_format function code-spacing in bltinmodule.c

2007-12-11 Thread Joseph Armbruster
All, Not sure if this is significant or not but the spacing of the builtin_format function is not consistent with the rest of the bltinmodule.c file. Joseph Armbruster ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/list

Re: [Python-Dev] patching asyncore and asynchat

2007-12-11 Thread Daniel Arbuckle
> From: "Giampaolo Rodola'" <[EMAIL PROTECTED]> > I remembered right now that there's a patch pending which should be > included in the trunk before solving issues related to py3k and/or > applying other changes: > http://bugs.python.org/issue1736190 > Since it solves a lot of older and newer async