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

Groups > comp.lang.python > #52821

Re: PEPs should be included with the documentation download

Newsgroups comp.lang.python
Date 2013-08-22 01:45 -0700
References <4bc4d258-1e12-4e1a-af9c-0019f099612f@googlegroups.com> <CAPTjJmoCwWk_n-rsxy9gJfJakcnoD8=9p6uFduSJALHzGs5n_A@mail.gmail.com> <mailman.90.1377107754.19984.python-list@python.org>
Message-ID <fe90da26-306f-41b7-8361-dc7505d201dc@googlegroups.com> (permalink)
Subject Re: PEPs should be included with the documentation download
From Aseem Bansal <asmbansal2@gmail.com>

Show all headers | View raw

On Wednesday, August 21, 2013 11:25:44 PM UTC+5:30, rand...@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.

PEP8 is referenced a lot but only a very small portion is included in the documentation (in the tutorial). I am a Python newbie and there may be other PEPs usually referenced which I might not be aware about. 

Maybe add selected PEPs to the documentation? I agree that adding rejected PEPs is no good but there may be PEPs worthy of addition to the documentation.

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