Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Terry Reedy <tjreedy@udel.edu>
Subject: Re: Python list code of conduct
Date: Wed, 03 Jul 2013 02:18:43 -0400
References: <kqtq4f$skq$1@news.grnet.gr> <mailman.4107.1372749724.3114.python-list@python.org> <kqu77d$s0f$1@news.grnet.gr> <CAMw+j7LvoFbzx-5MLrEiNjDXPutoGinm+abZXHsgn5Vi-p_Kgw@mail.gmail.com> <mailman.4116.1372766435.3114.python-list@python.org> <kquhld$lt5$1@news.grnet.gr> <CAMw+j7JSW7JSXuZuuAHNNswMRc0NVtPbCiaS=QibpvsRUEhAxg@mail.gmail.com> <kqum9j$bsu$1@ger.gmane.org> <a3704f85-2ef1-41e7-8fd1-8d7191f3fddb@email.android.com> <mailman.4125.1372798337.3114.python-list@python.org> <roy-D8C68F.19461302072013@70-1-84-166.pools.spcsdns.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
In-Reply-To: <roy-D8C68F.19461302072013@70-1-84-166.pools.spcsdns.net>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.4148.1372832343.3114.python-list@python.org>
Lines: 48
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:49705

On 7/2/2013 7:46 PM, Roy Smith wrote:
> In article <mailman.4125.1372798337.3114.python-list@python.org>,
>   Ned Deily <nad@acm.org> wrote:
>
>> If you find a bug in Python, don't send it to comp.lang.python; file
>> a bug report in the issue tracker.

I would revise this to "If you are have really found a bug in Python..."
How does a newbie know?

> I'm not sure I agree with that one, at least not fully.  It's certainly
> true that you shouldn't expect anybody to do anything about a bug unless
> you open an issue.
>
> On the other hand, I often find it useful to discuss things that I
> believe are bugs on c.l.p first.  Sometimes people will explain to me
> that I'm just doing it wrong.  Sometimes the discussion will end up
> with, "Yeah, that's a bug".

usually followed by "File a tracker issue" or "I opened an tracker issue 
for this." (I have done that several times, though I sometimes prefer a 
person learn how to do it themselves.)

 >   In either case, it serves as a good initial
> filter for whether I should file a bug or not, and the discussion is
> often educational.

Ask here first.
With a subject line that says 'I think ...' or "Problem with ...'
Advantages:

1. At least half the bugs newbies report are not. The tracker does not 
need the extra clutter.
2. Filing a tracker issue sometimes creates a 'mental investment' in the 
mis-perception, which leads to resentment upon explanation.
3. There are lots of people here ready to help and answer questions.
Any sensible question usually gets multiple responses, usually within a 
few hours or a day. (Invalid tracker reports may sit for days and get 
one short response.)
4. Explanations posted here benefit lots of people, rather than just 1.
5. A question posted here may elicit essential information, like which 
systems or which versions have the problem.
6. If you make an informed post to the tracker backed up by at least 
opinion, at least one tracker responder be in a better mode when responding.

--
Terry Jan Reedy