Re: Python Documentation (vs PHP stuff)

2005-05-12 Thread Paul Rubin
Roel Schroeven <[EMAIL PROTECTED]> writes: > In my experience, the user comments in many cases are almost useless. > Sometimes just confusing, sometimes contradicting each other, sometimes > even incorrect. Sometimes correct and useful too, but IMO that gets > drown between all the others. One thi

Re: Python Documentation (vs PHP stuff)

2005-05-12 Thread James Carroll
> > > Conclusion 1: if PHP is anything as awful as the manual, it is not for me. > > the whole idea that turning the manual into a wiki or a forum will solve all > problems is extremely naive. > Wha? I haven't done PHP for a couple of years, but when I really needed documentation, the PHP docs

Re: Python Documentation (vs PHP stuff)

2005-05-12 Thread Fredrik Lundh
> toolchain that adds relevant links to the generated HTML. e.g. oops. here's the pre-paste-and-cut-error text: toolchain that adds relevant links to the generated HTML. with that in place, external contributors can then place an annotation file on their own server, and send the li

Re: Python Documentation (vs PHP stuff)

2005-05-12 Thread Fredrik Lundh
Terry Reedy wrote: > Conclusion 1: if PHP is anything as awful as the manual, it is not for me. the whole idea that turning the manual into a wiki or a forum will solve all problems is extremely naive. on the other hand, having written lots of "manual enhancing material", I would love to be able

Re: Python Documentation (vs PHP stuff)

2005-05-12 Thread Roel Schroeven
Terry Reedy wrote: > Because of these two posts (and a few others) extolling the PHP > documentation, I decided to take a look for myself to see what the > fuss was about and whether I could get any ideas on how to improve > Python's docs. > > [...] > > Finally, 80% of the chapter/page consis

Re: Python Documentation (vs PHP stuff)

2005-05-11 Thread Ivan Van Laningham
Hi All-- Terry Reedy wrote: > > Conclusion 3: some people would apparently be happier with the Python docs > if they were combined into one Python Manual. This could be done as a > virtual anthology by writing a combined Table of Contents (with links) and > an Introduction discussing the various

Re: Python Documentation (vs PHP stuff)

2005-05-11 Thread Terry Reedy
"Christopher J. Bottaro" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > rbt wrote: >> Because PHP is such a 'thrown together' and 'bolted-on' language. If it >> didn't have *outstanding* documentation (which it does BTW), no one >> could even begin to understand how they got from a