A counter-proposal to __future__ in PEP 236
Michael Hudson
mwh21 at cam.ac.uk
Sun Mar 4 05:49:09 EST 2001
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.
Cheers,
M,
--
C++ is a siren song. It *looks* like a HLL in which you ought to
be able to write an application, but it really isn't.
-- Alain Picard, comp.lang.lisp
More information about the Python-list
mailing list