Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news.mixmin.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: "Martin v. Loewis" Newsgroups: comp.lang.python Subject: Re: When is PEP necessary? Date: Sat, 23 Apr 2011 22:31:06 +0200 Organization: 1&1 Internet AG Lines: 26 Message-ID: <4DB3370A.5020203@v.loewis.de> References: NNTP-Posting-Host: port-92-206-132-62.dynamic.qsc.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: online.de 1303590667 15146 92.206.132.62 (23 Apr 2011 20:31:07 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Sat, 23 Apr 2011 20:31:07 +0000 (UTC) To: Disc Magnet User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110402 Icedove/3.1.9 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:3926 Am 23.04.2011 14:16, schrieb Disc Magnet: > Is PEP necessary to add a new package to the standard library? A PEP is necessary if the proposed change is contentious. If there is widespread agreement that the change is desirable, no PEP is needed. > What if the community just wants to add a new module to an existing package? It depends on many questions: how does the author of the module think about that addition? If he vetoes it (for example), it doesn't matter what the community wants. Also, who is going to maintain it? Are there competing libraries that provide the same feature? etc. > What if only a new function has to be added to a module in the standard library? Likewise. Propose to contribute it, and see what happens. > What if only a line or two are to be added to a function in the > standard library? See above. It depends on the two lines. For example, changing the default source encoding to UTF-8 was a fairly small change, yet given past discussions, I felt that writing PEP 3120 was necessary. Regards, Martin