[IronPython] Issue Triage

Dino Viehland dinov at microsoft.com
Fri Dec 10 03:10:15 CET 2010

Thanks for doing this!  I've gone ahead and closed the first three.  I'm going to leave the compile() one open so it can get the right exception.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Richard Nienaber
Sent: Thursday, December 09, 2010 12:32 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Issue Triage

I've identified the following issues that I think are fixed:

PEP 342 broken -- generator.send() causes IPy exception<http://ironpython.codeplex.com/workitem/25574>
socket.gethostbyaddr("<broadcast>") broken under .NET 4.0 Beta<http://ironpython.codeplex.com/workitem/24495> (It looks like the correct behavior but the error message is different)
codecs.lookup errors with uppercase encoding names<http://ironpython.codeplex.com/workitem/20302>

And with this:

compile() incompatibility with CPython<http://ironpython.codeplex.com/workitem/22692>

It seems mostly fixed but a SyntaxError is thrown instead of an IndentationError


On Wed, Nov 24, 2010 at 4:54 AM, Jeff Hardy <jdhardy at gmail.com<mailto:jdhardy at gmail.com>> wrote:
There are over 1000 open issues on CodePlex
(http://ironpython.codeplex.com/workitem/list/basic), many of them
dating back to IronPython 1.0. A few people have wondered what they
can do to help IronPython without being familiar with the project. If
you're one of those people, then triaging issues would be a great
place to start - those issues should be checked against a modern
version of IronPython (preferably 2.7b1) to see if they are still

Also, I'd like to start getting a list of issues that are blockers for
releasing 2.7. If you have an issue that is blocking you in IronPython
2.7b1, report it on this list - I'll bump the priority up to high to
make sure it doesn't get missed.

Finally, if everyone could vote for this CodePlex issue
(http://codeplex.codeplex.com/workitem/25398) it would make it much
easier to share the list of blocking bugs. For now, Status = Open,
Impact = High, Release = 2.7. The ones already in the list are the
ones I plan on fixing myself.

- Jeff
Users mailing list
Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20101210/ec51c973/attachment.html>

More information about the Ironpython-users mailing list