Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.000
X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; '21,': 0.07; 'socket': 0.07; 'think,': 0.07; '22,': 0.09; 'bits': 0.09; 'pep': 0.09; 'rejected': 0.09; 'api': 0.11; 'python': 0.11; 'bug': 0.12; 'sections': 0.14; "wouldn't": 0.14; 'ah,': 0.16; 'compliant,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'internally': 0.16; 'personally,': 0.16; 'remedied': 0.16; 'subject:PEPs': 0.16; 'subject:download': 0.16; 'subject:included': 0.16; 'language': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'basically': 0.19; 'thu,': 0.19; 'seems': 0.21; '(the': 0.22; 'aug': 0.22; 'module,': 0.24; "i've": 0.25; 'compiled': 0.26; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'included': 0.31; 'that.': 0.31; 'embedding': 0.31; 'explained': 0.31; 'extending': 0.31; 'style': 0.33; 'subject:the': 0.34; 'subject:with': 0.35; 'beyond': 0.35; 'good.': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'really': 0.36; 'proposals': 0.36; 'subject:skip:d 10': 0.36; "didn't": 0.36; 'material': 0.36; 'useful': 0.36; 'should': 0.36; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'expect': 0.39; 'though,': 0.39; 'to:addr:python.org': 0.39; 'full': 0.61; 'information': 0.63; 'download.': 0.91; 'hill': 0.95; 'obtained': 0.96; '2013': 0.98
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rMQK3eWX6qrySYrKHWG3lcEavF4aeFwe/15AZQ5n5uQ=; b=i/GYXH32iNabrg0Tq1+conSI6KpCx9YJzUVWpFtn3cLgMRFd2yvwtD+uKhOPPoLz3h uXInnh3nm4obeIasEYGcpj2ISh+1+BjfcuNr8XDSXglpi6VENlxildHZePnjmJ4GpJl7 6G3nSEHFgF91iTFV495wd1wKLFMCk45JH1OzGe3Hckd0D8fukDo/62i/C30jo5OtW9JP bn0dKSlN6ITsrSDPe8S28a/ovUEwDwrJmpfDfZFuIKT1cYwLWK2rNfH8JXoN1forax7G vejvLoslM4H0jjTPprUj48AGE1ooPYHcNU0WxcpPqoUOQNm7taxs7JIZyPhCu7ZOEao+ HiJg==
MIME-Version: 1.0
X-Received: by 10.220.164.70 with SMTP id d6mr7598313vcy.19.1377111025312; Wed, 21 Aug 2013 11:50:25 -0700 (PDT)
In-Reply-To: <CADwdpyYbbMnbCZh+jqmUZE75uWXd4HbcTckY8Hfg+MbnnsAM2Q@mail.gmail.com>
References: <4bc4d258-1e12-4e1a-af9c-0019f099612f@googlegroups.com> <CAPTjJmoCwWk_n-rsxy9gJfJakcnoD8=9p6uFduSJALHzGs5n_A@mail.gmail.com> <1377107744.21484.12540441.3FF11C64@webmail.messagingengine.com> <CADwdpyYbbMnbCZh+jqmUZE75uWXd4HbcTckY8Hfg+MbnnsAM2Q@mail.gmail.com>
Date: Thu, 22 Aug 2013 04:50:25 +1000
Subject: Re: PEPs should be included with the documentation download
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
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.95.1377111034.19984.python-list@python.org>
Lines: 25
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1377111034 news.xs4all.nl 15913 [2001:888:2000:d::a6]:45712
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:52783

On Thu, Aug 22, 2013 at 4:15 AM, Jerry Hill <malaclypse2@gmail.com> wrote:
> On Wed, Aug 21, 2013 at 1:55 PM,  <random832@fastmail.us> wrote:
>> I think, though, that if there's any useful information that can be
>> obtained by reading accepted PEPs but not the documentation, or if
>> things are explained less clearly than in the PEPs, that's a bug in the
>> documentation, and should be remedied by adding to the documentation.
>
> Personally, the only PEPs I've used as reference material as PEP 8
> (the Python Style Guide), and PEP 249 (the Python Database API
> Specification v2.0).  If I recall correctly, one of the database
> adapters I used basically said that they were PEP 249 compliant, and
> didn't have much documentation beyond that.
>
> It seems to me that adding the PEPs to the compiled documentation
> would be a good thing.  They are at least as useful as the Language
> Reference or the Embedding and Extending Python sections that are
> already included.

Ah, yes, there are a few that would be good. But I don't really see
that all the internally bits (PEP 393, anyone?) and rejected proposals
(PEP 315) need to be in the download. I wouldn't expect the full set
of RFCs to be included with the docs for the socket module, so I
equally don't expect the PEPs to be included.

ChrisA