Why "from __future__" stinks; a counter-offer
John W. Baxter
jwbnews at scandaroon.com
Mon Mar 19 11:39:44 EST 2001
For the future, the time to complain about PEP contents is when the PEP
is posted, not after it has been posted, discussed, implemented, and the
result distributed.
For the Python 2.1 batch, late rants seem excusable, since the process
is new.
That said,
from __future__ import nested_scopes
works fine for me.
Which is just as well, because it means I can contentedly move on.
-----
Those who "do" PEPs will have noted a loud silence from me. That means
three things:
1. I'm lazy (but you knew that already)
2. I trust you and Guido to do the right thing, mostly. And I can deal
with the exceptions to that "mostly".
3. I still have to come to grips with SourceForge.
--John (getting back into weight training in preparation for
Programming Python 2nd Edition)
--
John W. Baxter Port Ludlow, WA USA jwbnews at scandaroon.com
More information about the Python-list
mailing list