On 2/10/2014 8:17 PM, Simon Forman wrote:
On 2/10/14, Mark Lawrence <breamore...@yahoo.co.uk> wrote:
[snip]
It would be absolutely amazing what Terry Reedy et al were to achieve if
they were to be given a helping hand fixing the 122 outstanding IDLE
bugs prior to adding anything to it.
That is the actually number if one searches by selecting Idle as the
component in Search Issues. There must be some bugs that are obsolete
and feature requests that should be rejected. There will still be many left.
Right, well, I've just gotten a hg checkout and I should have time
this week to work on (and perhaps close) at least one issue.
I do not think I am supposed to apply non-critical patches until 3.4 is
branched off from default.
Recommendations for issues to work on? (I don't have access to windows, so...)
What system *are* you on? One thing we specifically need at present is
someone willing to confirm bugs and test patches on a Mac for issues
that are not Mac-specific. (Ned Deily is pretty good about responding to
Mac-specific issues.) But we also need more testers for *nix and Windows.
What are you most interested in doing? Since you setup a repository and
want to close issues, you might focus on existing patches. If one does
the Idle issue search with Keyword: patch added, 66 are returned. There
might be other issues with patches that do not have the keyword checked.
If you want hints, I could add 'sforman' as nosy on issues I am most
interested in.
--
Terry Jan Reedy
_______________________________________________
IDLE-dev mailing list
IDLE-dev@python.org
https://mail.python.org/mailman/listinfo/idle-dev
