Why "from __future__" stinks; a counter-offer

[Tim Rowe]

In article <mailman.984966923.14984.python-list at python.org>, 
carribeiro at yahoo.com (Carlos Ribeiro) wrote:

<snip>

> Part of my rants are about the name of the module - __future__.py is a 
> bad and misleading name in my opinion. One alternative would be to call 
> this module __compiler__.py. It's a better name because:

My problems are more fundamental than the name, but if it ends up being 
done this way how about "__break_code__.py"? :-)