iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

This commit is contained in:
Tim Peters 2001-02-27 23:39:23 +00:00
parent 4efb4e9b2b
commit 77c92df29b
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-0236.txt
View File

@ -311,6 +311,17 @@ Questions and Answers
write a PEP addressing them. future_statement is aimed at a write a PEP addressing them. future_statement is aimed at a
different audience. 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 Copyright