[IronPython] The Road to 2.7 (Was: The Future of IronPython)
dinov at microsoft.com
Thu Oct 28 18:05:52 CEST 2010
> From: users-bounces at lists.ironpython.com [mailto:users-
> bounces at lists.ironpython.com] On Behalf Of Jeff Hardy
> Sent: Wednesday, October 27, 2010 10:58 PM
> To: Discussion of IronPython
> Subject: [IronPython] The Road to 2.7 (Was: The Future of IronPython)
> On Sun, Oct 24, 2010 at 4:45 AM, Lukas Cenovsky <cenovsky at bakalari.cz>
> > I'd like to help. What is the best place to start?
> Right now, we need to identify what's not working in 2.7B1 that needs to be
> in 2.7 final. The best thing to do would be to identify any issues that are
> causing you pain and bring them up on the list. Then we can decide what
> meets the bar for a 2.7 release (with issues that have patches getting priority,
> of course!). Dino, are there any issues that you know are in 2.7B1 that must
> be fixed for 2.7 final?
I think the biggest thing would be to look at the tests which are disabled due to
CodePlex bug #28171. Grepping the External.LCA_RESTRICTED\Languages\IronPython\27\Lib\test
Directory shows all of the places where things are disabled right now and they
all represent incompatibilities w/ CPython 2.7. Some of them may be things that
were broken all along and there's just tests for now. Others may be changes in
behavior between 2.6 and 2.7. They're also all lumped under this one bug right
now which makes it difficult to reason about the individual issues.
So there's lots of opportunity to either dive in and fix these, open individual bugs
for each of the issues, triage the issues, help identity which ones are more
important, see if they've been inadvertently fixed along the way to 2.7, etc...
And in general I'd say there's a lot of other bugs in the bug tracker that could be
fixed to deliver a really high quality 2.7.
More information about the Ironpython-users