[Python-Dev] 3.1 focus (was Re: for __future__ import planning)

Brett Cannon brett at python.org
Sat Oct 4 21:36:17 CEST 2008

[replying to both Georg and Martin]

On Sat, Oct 4, 2008 at 12:17 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Well, since for >95% of the (potential) Py3k users it is more important than
>> e.g. the import rewrite in Python (no stab at you intended, Brett), it is
>> something someone will have to get around to doing.

Don't worry, I realize my import work is approaching vaporware status
at this rate (still plugging away at it, though).

But you are right: helping people port to 3 will be the most important
thing we can help people with.

>> I'm not excusing myself; in fact, I'd be happy to work on this, but overall
>> the team "Python 3 advocacy and support" should consist of more than one
>> person.

I would definitely be willing to help.

So the mailing list is a good idea. Perhaps it should just be
python-porting so that it can also be used for people who have
problems with minor releases?

We could then have a /porting/ section to the site where we can
actually document after each release how to port to the newest

And as for 2 -> 3 stuff, should probably provide the expected steps to
port, tips for pure Python code (and how to write 2.6/3.0 compatible
code), extension modules, and make it clear what our overall plan is
(e.g. 3.2 probably being the truly stable release semantically).

> I think this has time. I'm (now) confident that people will port to
> Python 3 sooner rather than later, just because it's there. In fact,
> we have to be careful not to talk too many people into porting, since
> there will be some glitches which need to be resolved, and may not get
> resolved before 3.2 or so. So people with a natural wariness are advised
> to trust this wariness, or else all their concerns become
> self-fulfilling prophecies.

Yes, people should be warned that if they are not ready to make
changes after each Python release that are probably more than they are
used to between minor releases, they might to hold off for 3.1 or 3.2.
But I don't want to be too discouraging as that might stifle any
forward momentum we might have and potentially leave 3 flat before it
even gets going.


More information about the Python-Dev mailing list