Re: Python evolution: Unease
From: Terry Reedy (tjreedy_at_udel.edu)
Date: 01/06/05
- Next message: bearophileHUGS_at_lycos.com: "Re: Other notes"
- Previous message: It's me: "Re: Another PythonWin Excel question"
- Maybe in reply to: Iwan van der Kleyn: "Python evolution: Unease"
- Next in thread: Terry Reedy: "Re: Python evolution: Unease"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: python-list@python.org Date: Wed, 5 Jan 2005 19:37:01 -0500
"John Roth" <newsgroups@jhrothjr.com> wrote in message
news:10to8qulnc3vke1@news.supernews.com...
> I would like to contribute some documentation to Python.
> I've got the time, I write quite a bit, etc. I've got fairly
> strong opinions about some things that need to be documented,
> (such as all the new style class descriptor stuff from 2.2)
> and I have relatively little difficulty matching the existing style.
I would love to see the written better and in the manuals.
> However, I don't
> know TEX, Latex, CVS or Sourceforge. (The latter two are
> on my "learn sometime soon so I can put PyFIT where it belongs"
> list.)
Neither do I.
> I have no desire to install Perl to run the documentation toolchain.
> I also have no particular desire to write up a bunch of final
> format stuff and drop it on someone else to put into the latex
> format so it can be included.
Why not? If someone is willing to do the part that is easier for him
(format pre-written ascii text), why aren't you willing to do the part that
is easier for you (write the text)?
I am asking as someone who has done just that, at least on a micro scale of
occasional sentences in response to bug reports.
Terry J. Reedy
- Next message: bearophileHUGS_at_lycos.com: "Re: Other notes"
- Previous message: It's me: "Re: Another PythonWin Excel question"
- Maybe in reply to: Iwan van der Kleyn: "Python evolution: Unease"
- Next in thread: Terry Reedy: "Re: Python evolution: Unease"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|