On 8/10/2015 10:44 AM, Tal Einat wrote:
Indeed, this is great!
Perhaps this could be kept as an online document of some form so that it
could be kept up-to-date, e.g. a wiki page or a Google doc of some sort?
Google docs could allow you to control who can edit it, and e.g. allow
others to comment without actually editing the doc.
With two votes for updated availability, I will think about this.
On Sun, Aug 9, 2015 at 11:59 PM, Al Sweigart <a...@inventwithpython.com
<mailto:a...@inventwithpython.com>> wrote:
Thanks, this is a great list to consult to before I file new issues.
Idle has a big backlog and I don't want to add duplicates.
On Thu, Aug 6, 2015 at 7:18 PM, Terry Reedy <tjre...@udel.edu
<mailto:tjre...@udel.edu>> wrote:
A year or two ago, a couple of people announced a plan for a
database of Idle issues on a public site. I don't remember
anything about it later. Last year, I finally 'bit the bullet'
and created the following so I could close duplicates, add
myself as nosy to existing issues, and get an overview of what
needs to be done. Perhaps this will help others, but excuse the
sloppiness of notes meant to be private. If it is helpful, I
can repost occasionally when significantly changes. I am hoping
it will shrink, though I plan to convert some of the xxxxx
entries to real tracker entries.
----------------------------------------------
A listing of Idle tracker issues, 2015 Aug 6. Most items are listed
under a menu (or configure tab) item, actual or proposed. A few are
listed under idlelib or test.
* issue has patch to review.
# I uploaded patch to finish and commit.
IDLELIB
13504 meta-issue (check that each item is a separate issue, and
close)
--
Terry Jan Reedy
_______________________________________________
IDLE-dev mailing list
IDLE-dev@python.org
https://mail.python.org/mailman/listinfo/idle-dev
