New Q&A about why we're not introducing an entirely new statement.

pep-0236.txt

@@ -311,6 +311,17 @@ Questions and Answers
         write a PEP addressing them.  future_statement is aimed at a
         different audience.
 
+     Q: Overloading "import" sucks.  Why not introduce a new statement for
+        this?
+
+     A: Like maybe "lambda lambda nested_scopes"?  That is, unless we
+        introduce a new keyword, we can't introduce an entirely new
+        statement.  But if we introduce a new keyword, that in itself
+        would break old code.  That would be too ironic to bear.  Yes,
+        overloading "import" does suck, but not as energeticallly as the
+        alternatives -- as is, future_statements are 100% backward
+        compatible.
+
 
 Copyright