[Doc-SIG] A promise

Laurence Tratt laurie@eh.org
Mon, 27 Nov 2000 18:15:31 +0000

Andrew Kuchling wrote:

>>You have three main choices as to how to examine the Python code and work out
>>where the docstrings are (the docstrings themselves are something seperate and
>>probably easier to deal with): 
> 4) Use Jeremy's Tools/compiler (perhaps including a copy with the tool)
>    Pros: Handles both 2.0 and 1.5.2, I believe.  Someone is responsible for
>            maintaining it.
>    Cons: Not installed automatically by Python 2.0; must be packaged separately
>            for 1.5.2.
> We use it for parsing Python syntax in Quixote, and everything ported
> from 1.5.2 to 2.0 without effort.

That does look promising (the installation thing wouldn't worry me
particularly), although would I be an idiot if I said there's no obvious