Why "from __future__" stinks; a counter-offer

[Will Newton]

Aahz Maruch wrote:

> So far, no other person has actually come up with a scheme that addreses
> the problem at hand, as opposed to simply whining, suggesting minor and
> worthless variations, or putting forth even *more* complicated solutions.
> 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.

How often is this "from __future__" expected to be used?

Just experimental code written for bleeding edge versions of Python or a 
significant portion of code (that will eventually become legacy code)?