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: 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 Subject: Re: Python list code of conduct Date: Tue, 02 Jul 2013 17:07:19 -0700 References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: 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 In article , Roy Smith wrote: > In article , > Ned Deily 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