Managing the review queue

[KennyTM~]

On Mar 29, 11 04:04, bearophile wrote:
> Graham Fawcett:
>
>> I don't see the connection. '__future__' in Python isn't for experimental
>> features, nor is it for introducing stdlib changes. It's a way to 'import'
>> language features which become standard in later releases.
>
> But the end result is the same: if they find troubles in a feature present just in __future__, then I am sure they fix them before the feature becomes standard.
>
> Bye,
> bearophile

I disagree.

Python's future statement provides features that will certainly be 
enabled. It's a feature to provide smoother code compatibility with 
earlier versions. Every decision is pretty much settled when it is 
available in __future__, and the only step left is to enable it by default.

This is not the case for incubator/foo/experimental. There is no 
guarantee that the module must be voted in, nor the interface will be 
the same when transitioning to std.