Why "from __future__" stinks; a counter-offer

Tim Peters tim_one at email.msn.com
Tue Mar 20 00:36:29 EST 2001


[Greg Ewing]
>   from __future__ import no_future_statement
> 
> :-)

I expect it will be more like:

    from __future__ import directive_is_a_keyword
    directive future no_future_statement

Although, clearly, they will have to be given in that order <wink>.

if-you-ask-me-they're-both-ugly-ly y'rs  - tim





More information about the Python-list mailing list