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