Call for signatories for J2

[Paul Rubin]

Michael Sparks <zathras at thwackety.com> writes:
>    * Decorators incorporated via the __future__ mechanism
>    * A subset of people use them in earnest
>    * It's found that it would be useful to change the syntax whilst it's
>      still in the experimental __future__ phase. (As might've happened but
>      didn't with yield and generators)

I thought __future__ isn't for experimental features, but rather, it's
for definitely-accepted features that potentially break existing code,
for example by adding new keywords or changing the meaning of
something (the / division operator).  The idea is for a release or two
of the interpreter to signal a warning when an old program uses the
new keyword.