[Python-Dev] Weekly Python Patch/Bug Summary

Patch / Bug Summary ___ Patches : 404 open ( +5) / 3847 closed (+11) / 4251 total (+16) Bugs: 1059 open ( +3) / 6784 closed ( +8) / 7843 total (+11) RFE : 263 open ( +0) / 295 closed ( +1) / 558 total ( +1) New / Reopened Patches __ struni: F

Re: [Python-Dev] [Python-3000] optimizing [x]range

On 8/2/07, Stargaming <[EMAIL PROTECTED]> wrote: > >> made into an O(1) operation. here's a demo code (it should be trivial > >> to implement this in CPython) > [snipped algorithm] Did you taked into account that your patch is not backward compatible with py2.5?? Just try to do this with your patc

Re: [Python-Dev] Pythreads and BSD descendants

Cameron Laird schrieb: > Folklore that I remember so unreliably I avoid trying to repeat it here > held that Python threading had problems on BSD and allied Unixes. What's > the status of this? The problem that people run into again and again is the stack size. The BSDs allow for so little stack

Re: [Python-Dev] Building Python with CMake

On Friday 13 July 2007 16:11, Giovanni Bajo wrote: ... > Because it would be a single unified build system instead of having two > build systems like we have one (UNIX and Windows). > > Also, it would be much easier to maintain because Visual Studio projects > are generated from a simple descriptio

Re: [Python-Dev] make iter() return an empty iterator?

On 8/3/07, Steve Holden <[EMAIL PROTECTED]> wrote: > Kevin Jacobs <[EMAIL PROTECTED]> wrote: > > On 8/3/07, *Facundo Batista* <[EMAIL PROTECTED] > > > wrote: > > > > 2007/8/3, Andrew Bennetts <[EMAIL PROTECTED] > > >: > > > > > I don'

Re: [Python-Dev] Pythreads and BSD descendants

Cameron Laird wrote: > Folklore that I remember so unreliably I avoid trying to repeat it here > held that Python threading had problems on BSD and allied Unixes. What's > the status of this? I suspect the answer is, "Everything works, and the > only real problem ever was that *signals* have diff

Re: [Python-Dev] make iter() return an empty iterator?

Kevin Jacobs <[EMAIL PROTECTED]> wrote: > On 8/3/07, *Facundo Batista* <[EMAIL PROTECTED] > > wrote: > > 2007/8/3, Andrew Bennetts <[EMAIL PROTECTED] > >: > > > I don't really think there's much reason to make "iter()" > work.

Re: [Python-Dev] make iter() return an empty iterator?

On 8/3/07, Facundo Batista <[EMAIL PROTECTED]> wrote: > > 2007/8/3, Andrew Bennetts <[EMAIL PROTECTED]>: > > > I don't really think there's much reason to make "iter()" work. As you > say, > > What bad thing could happen if we make iter() work? If nothing, we > should ask ourselves: which is the m

[Python-Dev] make iter() return an empty iterator?

2007/8/3, Andrew Bennetts <[EMAIL PROTECTED]>: > I don't really think there's much reason to make "iter()" work. As you say, What bad thing could happen if we make iter() work? If nothing, we should ask ourselves: which is the more intuitive behaviour to expect of iter()? To raise an exception o

Re: [Python-Dev] NotImplemented comparisons

2007/8/2, Facundo Batista <[EMAIL PROTECTED]>: > > Given that you 'should' return an int, doing elsewise has undefined > > results. > > I'll fix decimal to always return sane values from __cmp__, :) Done, thanks again everybody! -- .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: ht

Re: [Python-Dev] Pythreads and BSD descendants

On Thu, Jul 26, 2007 at 04:08:37PM +, Cameron Laird wrote: > Folklore that I remember so unreliably I avoid trying to repeat it here > held that Python threading had problems on BSD and allied Unixes. What's > the status of this? I suspect the answer is, "Everything works, and the > only real

Re: [Python-Dev] [Python-3000] interaction between locals, builtins and except clause

On 7/26/07, Lisandro Dalcin <[EMAIL PROTECTED]> wrote: > Porting to Py3K, I modified a function like the followin, using a > trick for it working in Py2.x . > > def __iter__(self): > if self == _mpi.INFO_NULL: > return > try:range = xrange > except: pass

[Python-Dev] Pythreads and BSD descendants

Folklore that I remember so unreliably I avoid trying to repeat it here held that Python threading had problems on BSD and allied Unixes. What's the status of this? I suspect the answer is, "Everything works, and the only real problem ever was that *signals* have different semantics under Linux a

Re: [Python-Dev] make iter() return an empty iterator?

Georg Brandl wrote: > Sure, you could use ``iter(())`` or ``iter([])``, but for consistency's sake > wouldn't it make sense for ``iter()`` to return an empty iterator, as > ``str()`` > returns an empty string etc.? > > Georg There is a difference. >>> type(iter) >>> type(str) >>> type(int

Re: [Python-Dev] make iter() return an empty iterator?

Georg Brandl wrote: > Sure, you could use ``iter(())`` or ``iter([])``, but for consistency's sake > wouldn't it make sense for ``iter()`` to return an empty iterator, as > ``str()`` > returns an empty string etc.? I had no idea that "str()" or "int()" would do that. "file()" certainly doesn't!

[Python-Dev] make iter() return an empty iterator?

Sure, you could use ``iter(())`` or ``iter([])``, but for consistency's sake wouldn't it make sense for ``iter()`` to return an empty iterator, as ``str()`` returns an empty string etc.? Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number