Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #52780
| References | <4bc4d258-1e12-4e1a-af9c-0019f099612f@googlegroups.com> <CAPTjJmoCwWk_n-rsxy9gJfJakcnoD8=9p6uFduSJALHzGs5n_A@mail.gmail.com> <1377107744.21484.12540441.3FF11C64@webmail.messagingengine.com> |
|---|---|
| Date | 2013-08-21 14:15 -0400 |
| Subject | Re: PEPs should be included with the documentation download |
| From | Jerry Hill <malaclypse2@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.92.1377109280.19984.python-list@python.org> (permalink) |
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. -- Jerry
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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