'from __future__ import ...' overview

[Logan]

Is there a list with all 'from __future__ import ...' statements
(which lists all the statements, in which version of Python the
feature was introduced and in which version of Python it will become
the default behavior)?

I guess, normally such a list is not necessary because a new feature
needs its 'from __future__ import ...' statement only in the present
version of Python and will become default in the next version. But
e.g. 'from __future__ import division' is said to not become default
before Python 3.0.

Usually, I use A.M. Kuchling's "What's new in Python 2.x" articles
for that kind of stuff; but I thought, such a might exist somewhere
as a short reference.

Any links?

--
mailto: logan@phreaker(NoSpam).net

[Serge Orlov]

"Logan" <lo***@phreaker.nospam> wrote in message news:pa****************************@phreaker.nospa m...

Is there a list with all 'from __future__ import ...' statements
(which lists all the statements, in which version of Python the
feature was introduced and in which version of Python it will become
the default behavior)?

import __future__
print __future__.all_feature_names
print __future__.division

-- Serge

[Andrew Bennetts]

On Tue, Nov 25, 2003 at 01:09:09AM +0100, Logan wrote:

Is there a list with all 'from __future__ import ...' statements
(which lists all the statements, in which version of Python the
feature was introduced and in which version of Python it will become
the default behavior)?

Yes -- __future__.py in the python standard library.

-Andrew.

[Michael Hudson]

Logan <lo***@phreaker.nospam> writes:

Is there a list with all 'from __future__ import ...' statements
(which lists all the statements, in which version of Python the
feature was introduced and in which version of Python it will become
the default behavior)?

Yes: in __future__.py :-)

Cheers,
mwh

--
Lisp does badly because we refuse to lie. When people ask us if
we can solve insoluble problems we say that we can't, and because
they expect us to lie to them, they find some other language
where the truth is less respected. -- Tim Bradshaw, comp.lang.lisp