This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients 18z, cheryl.sabella, louielu, terry.reedy
Date 2017-06-28.00:58:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498611507.91.0.673868992054.issue30422@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is my current sorted list of IDLE issues.  It is a detailed map as opposed to the overview I posted before.

I spent a couple of days last week reviewing issues, making sure that all IDLE issues were marked category IDLE and that all with a patch were on my list, where they are marked by * after the issue number.  (Most everything else should be also.)  After closing 24 issues, there were 220 left, 115 with a patch to review.  I marked a few issues with ** for attention soon.

I obviously need help reviewing existing patches, and in some cases, turning them into github pull requests.

I still need to review and clean up the todos on the list.  I want to review TODO.txt to see what should be added (and then replace that file with this, under a different name).  There are also TODOs and XXXs in individual module files.

I posted a older version to idle-dev about Sept 2015 and will probably do so again.
History
Date User Action Args
2017-06-28 00:58:29terry.reedysetrecipients: + terry.reedy, louielu, cheryl.sabella, 18z
2017-06-28 00:58:27terry.reedysetmessageid: <1498611507.91.0.673868992054.issue30422@psf.upfronthosting.co.za>
2017-06-28 00:58:27terry.reedylinkissue30422 messages
2017-06-28 00:58:08terry.reedycreate