Dino Viehland wrote: > We haven't had much in the ways of discussing supporting Py3k features yet > and it might still be a little too early to do so. We have been following > some of the changes and we'll probably start following the changes a little > more closely. > > We also still have some catching up to do with v2.5 (1.1alpha has some > improved support but is still missing a couple of features) as well. So no > current plans yet but as that changes we'll be sure to let the community know. > Ok, great.
So your only settled plans are to continue to support Python 2.X features (including 2.6 ones ?), but no decision yet on how to deal with Python 3. Michael Foord http://www.voidspace.org.uk/python/index.shtml > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Baxter > Sent: Sunday, January 21, 2007 11:06 PM > To: Discussion of IronPython > Subject: Re: [IronPython] IronPython and Python 3 > > On 1/21/07, Michael Foord <[EMAIL PROTECTED]> wrote: > >> Hello all, >> >> What is the IronPython team's intention with respect to Python 2.X and >> Python 3 ? >> > > Note that Py3K is still a work in progress. Py2.6 will attempt to > support (through use of from __future__, &c) compatibility with 2.5 as > well as (hopefully) a lot of 3.0-isms. > _______________________________________________ > users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ > users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
