On 1/4/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 1/4/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > How about:
> >
> > except ExcType, e:
> > try:
> > # body
> > finally:
> > e = None
> > del e
> >
> > Then we get the
On 1/7/07, Collin Winter <[EMAIL PROTECTED]> wrote:
On 1/4/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 1/4/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > How about:
> >
> > except ExcType, e:
> > try:
> > # body
> > finally:
> > e
I've been thinking a little about how and where we'd add warnings to
2.6 and later for things that will break in 3.0. My first idea is
to add a command line option '-3' (or maybe '-warn3') implemented
as "from __future__ import py3k". We can then put code in that
optionally generates a warning
On 1/7/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> I've been thinking a little about how and where we'd add warnings to
> 2.6 and later for things that will break in 3.0. My first idea is
> to add a command line option '-3' (or maybe '-warn3') implemented
> as "from __future__ import py3k". We
At 09:14 PM 1/7/2007 -0600, Collin Winter wrote:
>On 1/4/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 1/4/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > > How about:
> > >
> > > except ExcType, e:
> > > try:
> > > # body
> > > finally:
> > >
On Monday 08 January 2007 16:50, Anthony Baxter wrote:
> I've been thinking a little about how and where we'd add warnings
> to 2.6 and later for things that will break in 3.0. My first idea
> is to add a command line option '-3' (or maybe '-warn3')
> implemented as "from __future__ import py3k". W
