Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #49705

Re: Python list code of conduct

From Terry Reedy <tjreedy@udel.edu>
Subject Re: Python list code of conduct
Date 2013-07-03 02:18 -0400
References (6 earlier) <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>
Newsgroups comp.lang.python
Message-ID <mailman.4148.1372832343.3114.python-list@python.org> (permalink)

Show all headers | View raw


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

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 06:37 +0300
  Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 15:15 +1000
    Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 08:57 +0300
      Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 17:21 +1000
        Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 12:40 +0300
          Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 12:06 +0200
          Re: OSError [Errno 26] ?!?! Dave Angel <davea@davea.name> - 2013-07-02 08:00 -0400
            Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 15:39 +0300
              Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 15:00 +0200
              Re: OSError [Errno 26] ?!?! Robert Kern <robert.kern@gmail.com> - 2013-07-02 14:58 +0100
                Re: OSError [Errno 26] ?!?! Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:19 +0000
                Re: Persistence of CGI (was: OSError [Errno 26] ?!?!) Tim Chase <python.list@tim.thechases.com> - 2013-07-02 19:57 -0500
              Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-02 16:51 +0100
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:42 +0000
              Re: Python list code of conduct Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-02 20:48 +0100
              Re: Python list code of conduct Skip Montanaro <skip@pobox.com> - 2013-07-02 15:33 -0500
              Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 13:52 -0700
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-02 19:46 -0400
                Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 17:07 -0700
                Re: Python list code of conduct Cameron Simpson <cs@zip.com.au> - 2013-07-03 10:10 +1000
                Bug reports [was Re: Python list code of conduct] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:52 +0000
                Re: Bug reports [was Re: Python list code of conduct] Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-03 02:12 +0100
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-03 18:02 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:03 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:15 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:23 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:52 +1000
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 20:11 +0000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 16:31 -0400
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 21:52 +0000
                IPv6 deployment by ISPs (was: Bug reports) Ben Finney <ben+python@benfinney.id.au> - 2013-07-04 11:15 +1000
                Re: Python list code of conduct Terry Reedy <tjreedy@udel.edu> - 2013-07-03 02:18 -0400
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-03 10:10 -0400
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 17:24 +0000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 08:39 +1000
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 06:18 +0000
              Re: Python list code of conduct Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-07-02 19:15 -0400
                Re: Python list code of conduct Neil Hodgson <nhodgson@iinet.net.au> - 2013-07-03 19:50 +1000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 10:39 +1000
                Re: Python list code of conduct rusi <rustompmody@gmail.com> - 2013-07-03 04:50 -0700
                Re: Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-03 15:18 +0100

csiph-web