On Sep 8, 2012, at 8:16 PM, Nick Coghlan wrote:
> On Sun, Sep 9, 2012 at 6:18 AM, Chris Jerdonek
> wrote:
>> This raises a related question. Where should we file issues for
>> Python-controlled things that are outside the scope of the cpython
>> repository (or the devguide) and that are not is
On Sun, Sep 9, 2012 at 6:18 AM, Chris Jerdonek wrote:
> This raises a related question. Where should we file issues for
> Python-controlled things that are outside the scope of the cpython
> repository (or the devguide) and that are not issues with the tracker
> (which has its own tracker -- the
On Thu, Sep 6, 2012 at 10:26 AM, R. David Murray wrote:
> On Thu, 06 Sep 2012 13:15:14 -0400, Terry Reedy wrote:
>> My understanding is that the tracker is for the cpython repository at
>> hg.python.org and my impression is that web code is elsewhere.
>
> That is true. However, the appearance an
On Thu, 06 Sep 2012 13:15:14 -0400, Terry Reedy wrote:
> On 9/5/2012 8:53 PM, Nick Coghlan wrote:
> > On Thu, Sep 6, 2012 at 8:13 AM, Terry Reedy wrote:
> >> I presume this suggestion does not belong on bugs.python.org, so I hope one
> >> of the docs people reading pydev will do something with it
On 9/5/2012 8:53 PM, Nick Coghlan wrote:
On Thu, Sep 6, 2012 at 8:13 AM, Terry Reedy wrote:
I presume this suggestion does not belong on bugs.python.org, so I hope one
of the docs people reading pydev will do something with it.
Why do you assume that?
My understanding is that the tracker is
On Thu, Sep 6, 2012 at 8:13 AM, Terry Reedy wrote:
> I presume this suggestion does not belong on bugs.python.org, so I hope one
> of the docs people reading pydev will do something with it.
Why do you assume that? Docs infrastructure suggestions can go on the
tracker under "enhancement", the sam
