Call for signatories for J2

Anthony Baxter anthonybaxter at gmail.com
Fri Aug 27 05:51:11 CEST 2004


On Thu, 26 Aug 2004 20:14:33 +0100, Michael Sparks
<zathras at thwackety.com> wrote:

>    1 The @pie implementation might stay as is.
>    2 The @pie implementation might stay, but require explicit activation
>      needing a __future__ statement. This to my mind is a good option - it
>      clearly marks the feature as experimental, making people shy away from
>      use unless they really do need it.
>    3 J2 might be accepted.
>    4 The feature might be ripped out
>    * etc...
> 
> Options 2 or 3 strike me as the best approach here - introduce a feature,
> mark it as experimental, with a large warning that it might change in the
> next release. That potentially allows the best of both worlds - people can
> use the feature in earnest, but do so on the understanding that the feature
> may change in a later release meaning that if they use it they have to be
> prepared to change their code. Furthermore if they release code using the
> feature they should be very careful how they use the feature.

That's not the way Python works - we don't rip stuff out once it's
been in a final release. from __future__ is added so that people can
turn on a new feature gradually, without their code being instantly
broken.



More information about the Python-list mailing list