Re: Documentation for python-evolution - where?

References	<3dnfr8-h6a.ln1@chris.zbmc.eu> <mailman.3523.1323652415.27778.python-list@python.org> <bdnhr8-aou.ln1@chris.zbmc.eu>
Date	2011-12-13 07:49 +1100
Subject	Re: Documentation for python-evolution - where?
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.3567.1323722970.27778.python-list@python.org> (permalink)

Show all headers | View raw

On Tue, Dec 13, 2011 at 3:40 AM,  <tinnews@isbd.co.uk> wrote:
> Actually I'm not sure if it's down to the docstrings because the help
> available from Python itself stops (not unreasonably) at the interface
> to the C library code.  What I was after (and you have told me where
> it is) was the functions/methods available from the C library.

Ah, yes, I know that problem! Let's see, how many high level
languages/libraries have I used that have simply exposed a lower-level
API without documenting it? REXX/REXXUtil and SysSetObjectData was the
first. More recently, Pike and the GTK/GTK2 modules. In between, oh so
many others.

Depending on how much is exposed and how transparent the local layer,
it may still be worth writing up some better documentation. Or if not,
it may be of value for the docs to incorporate a link to some
"upstream documentation", which would accomplish the same thing. (It's
a shot at immortality - get your name in a big project's revision
history!)

ChrisA

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

Thread

Documentation for python-evolution - where? tinnews@isbd.co.uk - 2011-12-11 22:28 +0000
  Re: Documentation for python-evolution - where? Chris Angelico <rosuav@gmail.com> - 2011-12-12 12:13 +1100
    Re: Documentation for python-evolution - where? tinnews@isbd.co.uk - 2011-12-12 16:40 +0000
      Re: Documentation for python-evolution - where? Chris Angelico <rosuav@gmail.com> - 2011-12-13 07:49 +1100

csiph-web