- Use the IronPython bug template - http://www.codeplex.com/IronPython/Wiki/V
iew.aspx?title=IronPython%20Bug%20Templa te. Something that’s been bugging me (yes…I did indeed just use that horrible pun) is the fact that we can’t act on some bugs because there’s not enough information contained in the reports. If you use this template we should have everything we need - If the bug blocks some major 3rd party package or application from running under IronPython, emphasize this in the bug report. We'll fix it much quicker if we know it blocks some major scenario
- Send mail to the IronPython mailing list. Time and time again I’ve seen Dino fix bugs reported on the mailing list the same day they’re reported. Also by doing this more IronPython users may vote on your bug which makes it a higher priority for us to fix
- Provide the simplest reproduction snippet you can. There have been a few bugs in the past which simply state “xyz doesn’t work under IronPython” where xyz might be some 3rd party application. In this case it can take us months to fix the bug as there’s a lot of bureaucracy involved in testing IronPython against non-Microsoft apps. It’s much better to provide us with a small Python code snippet independent of the 3rd party app which passes in CPython and fails under IronPython
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
knowbody's journalLog in Create a LiveJournal Account Learn more