Why "from __future__" stinks; a counter-offer

Vadim Chugunov chega_ at yahoo.com
Mon Mar 19 05:05:20 CET 2001


"Tim Peters" <tim_one at email.msn.com> wrote in message
news:mailman.984949523.1896.python-list at python.org...
> [Jason Orendorff]
> > Okay, nested scopes are a good idea.  Having the feature
> > "disabled by default" in 2.1 is a good idea.  But this
> > "from __future__" stuff isn't so hot.
> Did you read Martin's messages on this?  He picked "directive", and
submitted
> a patch to implement it (or some part of it).  But he didn't write a PEP,
so
> you'll have to search c.l.py and SourceForge for the relevant bits.  He
had
> in mind a more general facility, and in particular wants to specify
> source-file character encodings someday; I actively want not to conflate
> future_statements with "general directives" (although "directive future
xxx"
> might be OK -- alas, without a PEP, it's a non-starter).

But, surely, the PEP can be updated!   This "from __future__" syntax is
ugly, ugly, ugly!!!






More information about the Python-list mailing list