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

Groups > comp.lang.python > #49672

Re: Python list code of conduct

Path csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path <python-python-list@m.gmane.org>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.007
X-Spam-Evidence '*H*': 0.99; '*S*': 0.00; 'python,': 0.02; 'say,': 0.05; 'subject:Python': 0.06; 'subject:code': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'bug': 0.12; 'quoted': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'record,': 0.16; 'roy': 0.16; 'wrote:': 0.18; 'discussion': 0.18; 'first.': 0.19; 'not,': 0.20; 'issue.': 0.22; 'header:User-Agent:1': 0.23; 'certainly': 0.24; "shouldn't": 0.24; 'initial': 0.24; 'least': 0.26; 'header:X -Complaints-To:1': 0.27; 'point': 0.28; 'words': 0.29; 'subject:list': 0.30; "i'm": 0.30; 'with,': 0.31; 'file': 0.32; 'open': 0.33; 'url:python': 0.33; 'bugs': 0.33; 'role': 0.34; 'agree': 0.35; 'anybody': 0.35; 'case,': 0.35; 'one,': 0.35; 'but': 0.35; 'words,': 0.36; 'doing': 0.36; 'useful': 0.36; 'charset:us-ascii': 0.36; 'url:org': 0.36; 'should': 0.36; 'sometimes': 0.38; 'filter': 0.38; 'to:addr:python-list': 0.38; 'issue': 0.38; 'rather': 0.38; 'anything': 0.39; 'expect': 0.39; 'explain': 0.39; 'quote': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'either': 0.39; 'received:org': 0.40; 'forum': 0.61; 'discuss': 0.62; 'here': 0.66; 'believe': 0.68; 'smith': 0.68; 'received:204': 0.75; 'article': 0.77; 'educational.': 0.84; 'received:204.14': 0.84; 'hand,': 0.93
X-Injected-Via-Gmane http://gmane.org/
To python-list@python.org
From Ned Deily <nad@acm.org>
Subject Re: Python list code of conduct
Date Tue, 02 Jul 2013 17:07:19 -0700
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=US-ASCII
Content-Transfer-Encoding 7bit
X-Gmane-NNTP-Posting-Host 204.14.154.191
User-Agent MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.4138.1372810050.3114.python-list@python.org> (permalink)
Lines 28
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1372810051 news.xs4all.nl 15916 [2001:888:2000:d::a6]:42711
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:49672

Show key headers only | View raw

In article <roy-D8C68F.19461302072013@70-1-84-166.pools.spcsdns.net>,
 Roy Smith <roy@panix.com> 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'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".  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.

For the record, those are not my words, rather a quote from the 
"charter" for this forum on http://www.python.org/community/lists/.  I 
think the point of the quoted words is not to discourage discussion here 
but rather a reminder about the role of the issue tracker.  As you say, 
don't expect anybody to do anything about it without an issue on the 
tracker.

-- 
 Ned Deily,
 nad@acm.org

Back to comp.lang.python | Previous | Next — Previous 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