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

Groups > comp.lang.python > #52790

Re: PEPs should be included with the documentation download

Show all headers | View raw

On 8/21/2013 1:32 PM, Chris Angelico wrote:
> On Wed, Aug 21, 2013 at 3:14 PM, Aseem Bansal <asmbansal2@gmail.com> wrote:
>> Currently the documentation download includes a lot of things but PEPs are not its part. I wanted to suggest that PEPs should be included in the download. They are very much relevant to Python.
>
> The PEPs are kinda like the specs that Python is built from, rather
> than being end-user documentation; certainly most, if not all, are
> unnecessary to most use of Python. There's really no point downloading
> a whole pile of rejected PEPs as part of the crucial user-facing docs.

The manuals are intended to document current reality. Accepted PEPs 
document plans, often minus details. They do not get updated to reflect 
the initial implementation, let alone subsequent changes. Thus even

There are a few chapters in the manual that reference a PEP, either 
because the details are though to be too esoteric for the manual or 
becuase no one has yet gotten around to rewriting the material for the 
manual. (In the latter case, a patch should be welcome.) So there might 
be a reason to include a '(Highly) Selected PEPs' heading to the main 
page. PEP 8 might be a candidate, though it was originally intended as 
an internal style guide for the stdlib only.

-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

PEPs should be included with the documentation download Aseem Bansal <asmbansal2@gmail.com> - 2013-08-20 22:14 -0700
  Re: PEPs should be included with the documentation download Chris Angelico <rosuav@gmail.com> - 2013-08-22 03:32 +1000
    Re: PEPs should be included with the documentation download Aseem Bansal <asmbansal2@gmail.com> - 2013-08-22 01:39 -0700
      Re: PEPs should be included with the documentation download Terry Reedy <tjreedy@udel.edu> - 2013-08-22 18:46 -0400
  Re: PEPs should be included with the documentation download random832@fastmail.us - 2013-08-21 13:55 -0400
    Re: PEPs should be included with the documentation download Aseem Bansal <asmbansal2@gmail.com> - 2013-08-22 01:45 -0700
  Re: PEPs should be included with the documentation download Jerry Hill <malaclypse2@gmail.com> - 2013-08-21 14:15 -0400
  Re: PEPs should be included with the documentation download random832@fastmail.us - 2013-08-21 14:28 -0400
  Re: PEPs should be included with the documentation download Chris Angelico <rosuav@gmail.com> - 2013-08-22 04:50 +1000
  Re: PEPs should be included with the documentation download Terry Reedy <tjreedy@udel.edu> - 2013-08-21 16:15 -0400
  Re: PEPs should be included with the documentation download Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-08-21 20:27 -0400
  Re: PEPs should be included with the documentation download Ben Finney <ben+python@benfinney.id.au> - 2013-08-23 11:47 +1000
  Re: PEPs should be included with the documentation download Chris Angelico <rosuav@gmail.com> - 2013-08-23 11:54 +1000
    Re: PEPs should be included with the documentation download Neil Cerutti <neilc@norwich.edu> - 2013-08-23 13:19 +0000
  Re: PEPs should be included with the documentation download Ben Finney <ben+python@benfinney.id.au> - 2013-08-23 16:21 +1000
  Re: PEPs should be included with the documentation download Ned Deily <nad@acm.org> - 2013-08-23 01:14 -0700
  Re: PEPs should be included with the documentation download Ben Finney <ben+python@benfinney.id.au> - 2013-08-23 19:24 +1000

csiph-web