I've changed the home page on CodePlex and under the development section I've done the following:<div><ul><li>Renamed 'Contributing to IronPython' to 'Getting started with the source'</li><li>Created a new page called '<a href="http://ironpython.codeplex.com/wikipage?title=Contributing%20to%20IronPython&referringTitle=Home">Contributing to IronPython</a>' that includes the information from Dino and Jeff plus some other information.</li>
</ul><div>If more 'easy' bugs or unit tests are identified, I think they should probably go in the 'Contributing to IronPython' section because it might be easier to find for new contributors.</div><div><br>
</div><div>Richard</div><div><br></div><br><div class="gmail_quote">On Mon, Jan 24, 2011 at 3:32 AM, Dino Viehland <span dir="ltr"><<a href="mailto:dinov@microsoft.com">dinov@microsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
Jeff wrote:<br>
> For a nice easy fix to start with, take a look at<br>
> <a href="http://ironpython.codeplex.com/workitem/29928" target="_blank">http://ironpython.codeplex.com/workitem/29928</a>. You can either attach a<br>
> patch to the issue, or (preferably) create a fork on GitHub and send us a pull<br>
> request.<br>
<br>
</div>Here's some other bugs which look like they might be good to start on. Many of these are bug 28171 which is a catch-all bug for new tests in 2.7 that are broken. You can search the test dirs for these but here's the ones which looked like they could be easy with a couple more difficult ones mixed in. It also might be something good to pursue or triage away before 2.7 RTM.<br>
<br>
Modules:<br>
<a href="http://ironpython.codeplex.com/workitem/28315" target="_blank">http://ironpython.codeplex.com/workitem/28315</a><br>
test_functools:<br>
Couple of issues in here, first one might be easily fixed by adding setters which throw the correct exception, 2nd one might be implementing __reduce_ex__ directly on partial objects or maybe the stack trace will make the issue obvious.<br>
Test_struct: these look fairly straight forward, and will just be dealing w/ one module implementation in IronPython.<br>
<br>
Runtime libraries:<br>
Test_repeat in test_index.py (in the CPython test repro)<br>
Test_float_to_string in test_types.py<br>
Could be hard or easy but it's certainly easy to investigate - you just need to look at the string formatter code and see what it turns %g into.<br>
There's more string formatting failures in here as well which could be fairly easy<br>
Test_format.py has more string formatting bugs which could be fairly straight forward<br>
Test_xrange: this one even mentions the function which is broken<br>
<br>
Runtime types (these may be a little more difficult):<br>
Test_descr.py and test_collections.py both have some interesting failures around the type system and descriptors. Some of these may be easier (e.g. test_classmethods in test_descr.py) than others but might be interesting to look at for someone more interested into the type system side of things.<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
</div></div></blockquote></div><br></div>