A counter-proposal to __future__ in PEP 236

[Thomas Wouters]

On Sun, Mar 04, 2001 at 10:49:09AM +0000, Michael Hudson wrote:
> Thomas Wouters <thomas at xs4all.net> writes:

> > On Fri, Mar 02, 2001 at 09:38:04AM -0600, Lloyd Sommerer wrote:
> > 
> > > I should also point out that the "from  __future__ import..." is also
> > > confusing to a newbie, but others have said that already.
> > 
> > And that's exactly as it should be: you shouldn't use the experimental
> > feature(s) if you're a newbie :)

> Bzzt.  If your new to Python, you should always use nested scopes, so
> you don't have to unlearn the old behaviour when the new behaviour
> becomes the default in 2.2.

Bzzt. If you're new to Python, chances are (nowadays) that you are using a
book. None of the books will cover 2.1 until after 2.2 is out.

-- 
Thomas Wouters <thomas at xs4all.net>

Hi! I'm a .signature virus! copy me into your .signature file to help me spread!