[Python-3000] pre-PEP: Procedure for PEPs with Backwards-Incompatible Changes

[Neal Norwitz]

On 3/28/06, Ian Bicking <ianb at colorstudy.com> wrote:
>
> There seems to be a danger that Py3K is seen as a more friendly place to
> suggest changes than Python 2.x (or maybe that the python-3000 list is
> more friendly to these suggestions than py-dev), and so changes are
> brought up here even though they could be applied earlier.  This would
> be problematic in part because if a change *can* go in 2.x, it would be
> really good if it did, so that the move to 3.0 involves as few changes
> as possible.

I'm not concerned about that.  Everyone here will ensure that if a
feature should go into 2.x, it will.  The feature may be implemented
first in 3k, the PEP may be 3xxx, but when it's ready, it will migrate
to 2.x also.  This is important for moving to 3k.  We need to make the
migration as simple as possible.  "Backporting" these features is one
aspect of making it easier.

No one is forgetting about 2.x by any means.  There seemed to be
general consensus that there will be at least a couple more 2.x
releases.  Or maybe that was just my view and no one disagreed. :-)

n