Mailman 3 August 2005 - Doc-SIG

Re: [Doc-SIG] Creating howto directory in Python CVS
by Laura Creighton Aug. 29, 2005

Aug. 29, 2005

In a message of Mon, 29 Aug 2005 14:16:36 EDT, "A.M. Kuchling" writes: >On Mon, Aug 29, 2005 at 07:38:15PM +0200, Laura Creighton wrote: >> want to bother him personally about a personal page. If they were >> on python.org I would have sent my 'wish you had explained this >> better' bit and my example of how to for sure. > >Really? Hm, I should add a paragraph that encourages people to submit >comments. (I expect comments from everything I publish on the web, >though I don't necessarily answer them -- instead they pile up in a >mailbox until the next time I work on whatever the page is.) You already have this paragraph. I read it. I wrote the mail to you. I then said, oh what the heck, it is a small change and I already know the man is so damn busy with more important things that my tiny addition looks like whining. And I do not want amk to think that I am a whiner. So I never sent it to you. I have no idea how often this happens, but I am willing to admit it, which I figure is sort of rare. Laura

1 0

Re: [Doc-SIG] Creating howto directory in Python CVS
by Laura Creighton Aug. 29, 2005

Aug. 29, 2005

In a message of Mon, 29 Aug 2005 14:03:39 EDT, "Fred L. Drake, Jr." writes: >On Monday 29 August 2005 13:38, Laura Creighton wrote: > > I had a small problem with reg-exp how to the other day. > > what decided me against report it to amk was the idea that I didn't > > want to bother him personally about a personal page. If they were > > on python.org I would have sent my 'wish you had explained this > > better' bit and my example of how to for sure. > >Good point. I suspect many people would rather complain to an "anonymous >" >address or issue collector. Being able to report problems in the Python >collector or to the docs at python.org address might help gather suggesti >ons >and error reports. > > > -Fred > >-- >Fred L. Drake, Jr. <fdrake at acm.org> By the way, my use case was 'having split your thing nicely up into 6 named groups, how do you write them out again as the same groups in a different order' Ie take a file: dog animal bites fish animal doesn't book object doesn't and turn it into: an animal that bites is a dog an animal that doesn't bite is a fish an object that doesn't bite is a book .... I actually was stuffing docstrings from python2.4 into Pypy. :-) There must be a way to do this which deosn't involve assigning to python variables, but i never found it in time. But after futzing around a bunch, i concluded that the regexp how to was short on how to actually batch precess a file making a set of substutions based on the matches you found. Which I wish I knew how to do better. thanks all, Laura

1 0

Re: [Doc-SIG] Creating howto directory in Python CVS
by Laura Creighton Aug. 29, 2005

Aug. 29, 2005

In a message of Mon, 29 Aug 2005 13:30:02 EDT, "Fred L. Drake, Jr." writes: >On Monday 29 August 2005 09:28, A.M. Kuchling wrote: > > Actually they're on amk.ca now. People find them pretty well -- type > > "regular expression" into Google and the HOWTO is the top hit; it's > > the second hit for "regular expressions". I'd have no objection to > > moving them to python.org hosting, but no pressing desire to do so. > >Ok, that's really an unrelated issue anyway. If people find them without > >problems, there's no need to change it and break links. I had a small problem with reg-exp how to the other day. what decided me against report it to amk was the idea that I didn't want to bother him personally about a personal page. If they were on python.org I would have sent my 'wish you had explained this better' bit and my example of how to for sure. Laura

3 2

Creating howto directory in Python CVS
by A.M. Kuchling Aug. 29, 2005

Aug. 29, 2005

I'd like to (finally) check in the HOWTOs into the main Python CVS; I've begun writing new ones like the Unicode HOWTO, and it would be good if more people had access to them. Since they probably won't be added to the documentation set, they should go in nondist/ in CVS. nondist/howto/ seems too high-level, though; any objection to creating nondist/doc/ and putting a howto/ directory in it? Then we have a natural place to add other documentation that isn't part of the core set. --amk

3 5