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


Groups > comp.lang.python > #49655

Re: Python list code of conduct

From Ned Deily <nad@acm.org>
Subject Re: Python list code of conduct
Date 2013-07-02 13:52 -0700
References (4 earlier) <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>
Newsgroups comp.lang.python
Message-ID <mailman.4125.1372798337.3114.python-list@python.org> (permalink)

Show all headers | View raw


In article <a3704f85-2ef1-41e7-8fd1-8d7191f3fddb@email.android.com>,
 Steve Simmons <square.steve@gmail.com> wrote:
> Does this list have a code of conduct or a netiqeutte (sp?) 
> statement/requirement? 

>From http://www.python.org/community/lists/

comp.lang.python

comp.lang.python is a high-volume Usenet open (not moderated) newsgroup 
for general discussions and questions about Python. You can also access 
it as a mailing list through python-list.

Pretty much anything Python-related is fair game for discussion, and the 
group is even fairly tolerant of off-topic digressions; there have been 
entertaining discussions of topics such as floating point, good software 
design, and other programming languages such as Lisp and Forth.

Most discussion on comp.lang.python is about developing with Python, not 
about development of the Python interpreter itself. Some of the core 
developers still read the list, but most of them don't. Occasionally 
comp.lang.python suggestions have resulted in an enhancement proposal 
being written, leading to a new Python feature. If you find a bug in 
Python, don't send it to comp.lang.python; file a bug report in the 
issue tracker.

Items posted on the Usenet group appear on the mailing list, and vice 
versa (bidirectional gateway). Due to the mysteries of Usenet, the order 
in which items show up may vary.

Rudeness and personal attacks, even in reaction to blatant flamebait, 
are strongly frowned upon. People may strongly disagree on an issue, but 
usually discussion remains civil. In case of an actual flamebait 
posting, you can ignore it, quietly plonk the offending poster in your 
killfile or mail filters, or write a sharp but still-polite response, 
but at all costs resist the urge to flame back. Generally 
comp.lang.python is a high-signal, low-noise group. It's also a 
high-traffic group, running at around 200 posts per day.

There are several different archives:
   ?  Google Groups archive of comp.lang.python
   ?  python.org archive of python-list
   ?  gmane.org archive of python-list

-- 
 Ned Deily,
 nad@acm.org

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