Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-24 Thread Guido van Rossum
On Sun, Feb 24, 2008 at 7:02 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > On Sun, Feb 24, 2008 at 6:57 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 5:59 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > > > On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PRO

Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-24 Thread Neal Norwitz
On Sun, Feb 24, 2008 at 6:57 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Sat, Feb 23, 2008 at 5:59 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]> > wrote: > > > > > > I do think map() and filter() should issue a

Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-24 Thread Guido van Rossum
On Sat, Feb 23, 2008 at 5:59 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > > I do think map() and filter() should issue a warning under -3 when the > > first arg is None. (Or does 2to3 detect this now?) > > Wha

Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-24 Thread Collin Winter
On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > I don't think a -3 warning for oct or hex would do any good. > > I do think map() and filter() should issue a warning under -3 when the > first arg is None. (Or does 2to3 detect this now?) 2to3 does detect that: it wi

Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-23 Thread Neal Norwitz
On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > I do think map() and filter() should issue a warning under -3 when the > first arg is None. (Or does 2to3 detect this now?) What's wrong with filter(None, seq)? That currently works in 3k: >>> filter(None, range(5

Re: [Python-Dev] future_builtins

2008-02-23 Thread Guido van Rossum
On Sat, Feb 23, 2008 at 11:34 AM, Eric Smith <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > On Sat, Feb 23, 2008 at 9:01 AM, Eric Smith > > <[EMAIL PROTECTED]> wrote: > >> Guido van Rossum wrote: > >> > I don't think a -3 warning for oct or hex would do any good. > >> > >> I'm cur

Re: [Python-Dev] future_builtins

2008-02-23 Thread Eric Smith
Guido van Rossum wrote: > On Sat, Feb 23, 2008 at 9:01 AM, Eric Smith > <[EMAIL PROTECTED]> wrote: >> Guido van Rossum wrote: >> > I don't think a -3 warning for oct or hex would do any good. >> >> I'm curious as to why. oct and hex have different behavior in 3.0, >> which is what I thought -3

Re: [Python-Dev] future_builtins

2008-02-23 Thread Guido van Rossum
On Sat, Feb 23, 2008 at 9:01 AM, Eric Smith <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > I don't think a -3 warning for oct or hex would do any good. > > I'm curious as to why. oct and hex have different behavior in 3.0, > which is what I thought -3 was for. hex might be overkill,

Re: [Python-Dev] future_builtins

2008-02-23 Thread Eric Smith
Guido van Rossum wrote: > I don't think a -3 warning for oct or hex would do any good. I'm curious as to why. oct and hex have different behavior in 3.0, which is what I thought -3 was for. hex might be overkill, as the only differences are the "L" and the __hex__ behavior. But oct is always

Re: [Python-Dev] future_builtins (was: Backporting PEP 3127 to trunk)

2008-02-23 Thread Guido van Rossum
I don't think a -3 warning for oct or hex would do any good. I do think map() and filter() should issue a warning under -3 when the first arg is None. (Or does 2to3 detect this now?) On Sat, Feb 23, 2008 at 6:06 AM, Eric Smith <[EMAIL PROTECTED]> wrote: > Georg Brandl wrote: > > Eric Smith schri