Why "from __future__" stinks; a counter-offer

[Greg Ewing]

Aahz Maruch wrote:
> 
> One of the nice things about this solution is that if it is decided to be
> an ugly wart, it can be easily dropped for Python 2.2.

So we may one day find ourselves writing

  from __future__ import no_future_statement

:-)

-- 
Greg Ewing, Computer Science Dept, University of Canterbury,	  
Christchurch, New Zealand
To get my email address, please visit my web page:	  
http://www.cosc.canterbury.ac.nz/~greg