A counter-counter-proposal for PEP 236: #pragma( nested_scopes)

Jeremy Hylton jeremy at alum.mit.edu
Thu Mar 1 21:52:41 CET 2001


>>>>> "FL" == Fredrik Lundh <fredrik at pythonware.com> writes:

  FL> But Python isn't supposed to grow lots of pragma-style settings.
  FL> There shouldn't be any "other things".  There Should Only Be One
  FL> Language.

  FL> We're talking about two kinds of "directives" here:

  [skipping #1]  

  FL> -- Experimental compiler features, which if successful will
  FL>    become standard in the next release.  Again, "directive"
  FL>    doesn't work, since it makes "experimental" stuff look
  FL>    "optional". 

A word of clarification: __future__ isn't about experimental
features.  Instead it is for bleeding edge users to use a new feature
in release X even though the feature won't be standard until release
Y, where X < Y.

If we want to do experimental stuff, we should probably do something
like:

from __possible_world__ import __future__
from __future__ import ...

Jeremy




More information about the Python-list mailing list