[Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

Neal Norwitz nnorwitz at gmail.com
Wed May 23 08:07:29 CEST 2007

On 5/22/07, Steve Howell <showell30 at yahoo.com> wrote:
> But since you mentioned conversion, our system is a
> good example of a shop that will be running multiple
> versions of Python side by side for many years.  We'll
> cut over new components to Py3k, and then we'll
> gradually upgrade legacy components.  And, of course,
> some of those components will want to use the same
> common modules.

Once we get a solid 3.0 (probably in beta), we will focus more energy
on dealing with these sorts of problems.

I can see there being a compatibility module that could fix things up
to run with Python 2.x (*) - 3.0.  I don't know if that will be
distributed by the core or by a third party.  There are many people
that care about this issue.  It's not being forgotten.  We just
haven't gotten to it yet.  2.6 and 3.0 are a year away, probably more.

(*) probably between 2.2 and 2.4 depending on how hard it is to support.

Pretty soon I'll start focusing on getting 2.6 in shape to help ease
the transition.


More information about the Python-3000 mailing list