On 8/14/2015 1:33 PM, phil jones wrote:
OK. Understood.
Just seems that so many tools these days, from Trac to GitHub integrate
wiki with the tracker, allowing you to hand-roll custom lists like these
but still easily integrate / hyperlink them into the tracker.
Going to Google Docs seems a f
OK. Understood.
Just seems that so many tools these days, from Trac to GitHub integrate
wiki with the tracker, allowing you to hand-roll custom lists like these
but still easily integrate / hyperlink them into the tracker.
Going to Google Docs seems a fairly awkward way to do this. Is there a wik
On 8/14/2015 11:09 AM, phil jones wrote:
If IDLE *was* on, say, GitHub, wouldn't a public up-to-date bug / todo /
issue list and wiki be part of that?
The Python tracker can give you such a list. Go to
https://bugs.python.org/issue?@template=search&status=1
select Components IDLE and go. At th
If IDLE *was* on, say, GitHub, wouldn't a public up-to-date bug / todo /
issue list and wiki be part of that?
Phil
On 14 August 2015 at 11:52, Terry Reedy wrote:
> 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
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 commen
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.
On Su
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 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 r
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 overv
