From goodger at python.org Tue Dec 2 22:09:31 2003 From: goodger at python.org (David Goodger) Date: Tue Dec 2 22:09:35 2003 Subject: [Doc-SIG] New concept of "commands"? In-Reply-To: <3FBE0258.1010103@gmx.net> References: <3FBBFAED.9060301@gmx.net> <3FBC2D15.1040506@python.org> <3FBC8846.5040204@gmx.net> <3FBDAA2D.8030409@python.org> <3FBE0258.1010103@gmx.net> Message-ID: <3FCD53EB.10807@python.org> Luc Saffre wrote: > But I would like to come back to my original idea of "commands". > After all these discussions I still believe that this would be an > elegant extension slot for reStructuredText. I am unconvinced of the necessity (see below). > It would also make custom URI schemes unnecessary. My suggestion of custom URI schemes was to avoid or minimize any new syntax. A small tweak to an existing construct is easier to accept than a whole new construct. > Consider also that commands would enhance readability for specific > contexts:: > > Don't execute [=fileref /setup.py]_ because it does not work yet. > > is much more readable than:: > > Don't execute `setup.py <:fileref:/setup.py>`_ because it does > not work yet. I would write it either using substitutions and a directive:: Don't execute |setup.py| because it does not work yet. .. |setup.py| fileref:: /setup.py Or using interpreted text roles:: Don't execute :fileref:`setup.py` because it does not work yet. Directives and roles are Docutils' extension mechanisms. Before adding another mechanism, I'd like to see an example that clearly isn't covered by the existing two. > I did not yet find time to study the parser's code in order to check > how expensive my idea would be. The expense of implementing an idea in code is not so important. The cost to the markup itself is the important thing. The idea and its syntax must be necessary, non-redundant, and elegant. I don't think we're at that point yet. -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From luc.saffre at gmx.net Wed Dec 3 04:52:41 2003 From: luc.saffre at gmx.net (Luc Saffre) Date: Wed Dec 3 04:52:49 2003 Subject: [Doc-SIG] New concept of "commands"? In-Reply-To: <3FCD53EB.10807@python.org> References: <3FBBFAED.9060301@gmx.net> <3FBC2D15.1040506@python.org> <3FBC8846.5040204@gmx.net> <3FBDAA2D.8030409@python.org> <3FBE0258.1010103@gmx.net> <3FCD53EB.10807@python.org> Message-ID: <3FCDB269.2030108@gmx.net> Tilt! Thank you, David. You are right. There is no necessity for commands. "Interpreted text roles" was the concept that I missed. I had not seen http://docutils.sourceforge.net/spec/rst/interpreted.html or perhaps I needed your example to understand that roles are what I'm looking for. Okay, I hope I will soon find time to implement some examples of application-defined roles in WebMan. Luc On 3/12/2003 5:09, David Goodger wrote: > Luc Saffre wrote: > > Consider also that commands would enhance readability for specific > > contexts:: > > > > Don't execute [=fileref /setup.py]_ because it does not work yet. > > > > is much more readable than:: > > > > Don't execute `setup.py <:fileref:/setup.py>`_ because it does > > not work yet. > > I would write it either using substitutions and a directive:: > > Don't execute |setup.py| because it does not work yet. > > .. |setup.py| fileref:: /setup.py > > Or using interpreted text roles:: > > Don't execute :fileref:`setup.py` because it does not work yet. > > Directives and roles are Docutils' extension mechanisms. Before > adding another mechanism, I'd like to see an example that clearly > isn't covered by the existing two. From franks at mcs.anl.gov Fri Dec 5 12:34:02 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Fri Dec 5 12:34:06 2003 Subject: [Doc-SIG] sub/superscript directive? Message-ID: <3FD0C18A.4010300@mcs.anl.gov> Dear RST gurus, I'm trying to use the (somewhat undocumented) sub/superscript directives in RST, but I always seem to end up with a space between the sub/superscripted character and the one in front of it in the HTML output. For example, what works is : A `i`:sub: but this leaves a space between the A and the subscripted i. Removing the space between "A" and "`i`:sub:" doesn't get throught the RST interpreter.... I'm using the buildhtml.py script to generate the HTML. Thanks, Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From goodger at python.org Fri Dec 5 13:02:47 2003 From: goodger at python.org (David Goodger) Date: Fri Dec 5 13:02:50 2003 Subject: [Doc-SIG] sub/superscript directive? In-Reply-To: <3FD0C18A.4010300@mcs.anl.gov> References: <3FD0C18A.4010300@mcs.anl.gov> Message-ID: <3FD0C847.1060900@python.org> Frank Siebenlist wrote: > I'm trying to use the (somewhat undocumented) sub/superscript > directives Not directives: interpreted text roles. > in RST, but I always seem to end up with a space between the > sub/superscripted character and the one in front of it in the HTML > output. I added a tip to the docs: . -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From franks at mcs.anl.gov Fri Dec 5 13:16:34 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Fri Dec 5 13:16:40 2003 Subject: [Doc-SIG] sub/superscript directive? In-Reply-To: <3FD0C847.1060900@python.org> References: <3FD0C18A.4010300@mcs.anl.gov> <3FD0C847.1060900@python.org> Message-ID: <3FD0CB82.6060604@mcs.anl.gov> David Goodger wrote: > Frank Siebenlist wrote: > >> I'm trying to use the (somewhat undocumented) sub/superscript >> directives > > > Not directives: interpreted text roles. > >> in RST, but I always seem to end up with a space between the >> sub/superscripted character and the one in front of it in the HTML >> output. > > > I added a tip to the docs: > . Works - thanks! -Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From u_schlaepfer at bluewin.ch Sat Dec 6 09:26:42 2003 From: u_schlaepfer at bluewin.ch (Ueli =?ISO-8859-1?Q?Schl=E4pfer?=) Date: Sat Dec 6 09:26:48 2003 Subject: [Doc-SIG] sub/superscript directive? In-Reply-To: <3FD0C847.1060900@python.org> References: <3FD0C18A.4010300@mcs.anl.gov> <3FD0C847.1060900@python.org> Message-ID: <20031206152642.4a9f86a6.u_schlaepfer@bluewin.ch> Hi there, On Fri, 05 Dec 2003 13:02:47 -0500 David Goodger wrote: > Frank Siebenlist wrote: > > I'm trying to use the (somewhat undocumented) sub/superscript > > directives [...] > > in RST, but I always seem to end up with a space between the > > sub/superscripted character and the one in front of it in the HTML > > output. > > I added a tip to the docs: > . I just checked it out. While it's definitely a good thing to see working examples, they clearly (at least IMHO) violate one of the primary goals of reST: plaintext readability. I'd suggest to extend the tip by at east mentioning substitutions. As of now, the tip reads: .. Tip:: Whitespace or punctuation is required around interpreted text, but often not desired with subscripts & superscripts. Backslash-escaped whitespace can be used; the whitespace will be removed from the processed document:: H\ :sub:`2`\ O E = mc\ :sup:`2` See `the reStructuredText spec`__ for further information. __ ./reStructuredText.html#character-level-inline-markup How about modifying it to something like .. Tip:: Whitespace or punctuation is required around interpreted text, but often not desired with subscripts & superscripts. Backslash-escaped whitespace can be used; the whitespace will be removed from the processed document:: H\ :sub:`2`\ O E = mc\ :sup:`2` In such cases, readability of the plain text can be greatly improved with substitutions:: The chemical formula for pure water is |H20|. .. |H20|: H\ :sub:`2`\ O See `the reStructuredText spec`__ for further `information on character-level makeup`__ and on the `substitution mechanism`__. __ ./reStructuredText.html __ ./reStructuredText.html#character-level-inline-markup __ ./reStructuredText.html#substitution-references -- Ueli Schl?pfer From goodger at python.org Sat Dec 6 11:30:21 2003 From: goodger at python.org (David Goodger) Date: Sat Dec 6 11:30:23 2003 Subject: [Doc-SIG] sub/superscript directive? In-Reply-To: <20031206152642.4a9f86a6.u_schlaepfer@bluewin.ch> References: <3FD0C18A.4010300@mcs.anl.gov> <3FD0C847.1060900@python.org> <20031206152642.4a9f86a6.u_schlaepfer@bluewin.ch> Message-ID: <3FD2041D.4030805@python.org> David Goodger wrote: >> I added a tip to the docs: >> . Ueli Schl?pfer wrote: > I just checked it out. While it's definitely a good thing to see > working examples, they clearly (at least IMHO) violate one of the > primary goals of reST: plaintext readability. I'd suggest to extend the > tip by at east mentioning substitutions. Looks good to me! Checked in, thanks. -- David Goodger From franks at mcs.anl.gov Tue Dec 9 13:11:53 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Tue Dec 9 13:12:06 2003 Subject: [Doc-SIG] directive for flexible literate programming support? Message-ID: <3FD61069.6070707@mcs.anl.gov> I'm currently using rst to write haskell literate programs. The haskell interpreter will recognize the text as code if a line starts with a ">". To set the code apart, I use "Literal Blocks" for the code snippets. Unfortunately, a literate block has to be indented, which doesn't work well with the interpreter. So I use a one line script to change the " >" into ">" to get rid of the space in the first column, before feeding it to the interpreter. This is not convenient and not very elegant... Are there maybe other existing ways to make this easier? If not, one option could be to introduce a directive that would specify how to recognize literate blocks, like: .. literate-block :: ">" which would indicate that for rest of this file, a literate block could also be identified with a block where the lines start with ">" besides the normal whitespace indentation. Thanks, Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From aahz at pythoncraft.com Tue Dec 9 13:41:53 2003 From: aahz at pythoncraft.com (Aahz) Date: Tue Dec 9 13:41:58 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <3FD61069.6070707@mcs.anl.gov> References: <3FD61069.6070707@mcs.anl.gov> Message-ID: <20031209184153.GA5065@panix.com> On Tue, Dec 09, 2003, Frank Siebenlist wrote: > > If not, one option could be to introduce a directive that would specify how > to recognize literate blocks, like: > > .. literate-block :: ">" > > which would indicate that for rest of this file, a literate block could > also be identified with a block where the lines start with ">" besides the > normal whitespace indentation. Actually, what it would substitute for is Python's interactive mode; reST already understands:: >>> x = 1 as belonging to a literal block that comes from Python's interactive mode. The main problem for your request is the interface; do we only allow simple strings? What about regexes? What about plug-in code? -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. From franks at mcs.anl.gov Tue Dec 9 14:31:08 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Tue Dec 9 14:31:41 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <20031209184153.GA5065@panix.com> References: <3FD61069.6070707@mcs.anl.gov> <20031209184153.GA5065@panix.com> Message-ID: <3FD622FC.8010707@mcs.anl.gov> Aahz wrote: > On Tue, Dec 09, 2003, Frank Siebenlist wrote: > >>If not, one option could be to introduce a directive that would specify how >>to recognize literate blocks, like: >> >>.. literate-block :: ">" >> >>which would indicate that for rest of this file, a literate block could >>also be identified with a block where the lines start with ">" besides the >>normal whitespace indentation. > > > Actually, what it would substitute for is Python's interactive mode; > reST already understands:: > > >>> x = 1 Yes, I looked at that when I started - too bad for my case that "it" was decided to use three ">" instead of a single one ;-) > as belonging to a literal block that comes from Python's interactive > mode. The main problem for your request is the interface; do we only > allow simple strings? What about regexes? What about plug-in code? Just for my case and probably the formatting of literate code snippets in general, a simple string would suffice. I can't think of any use cases where you would need the added complexity of regexes, while I don't know what "plug-in code" is but is sounds scary from a complexity point of view... -Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From goodger at python.org Tue Dec 9 17:53:30 2003 From: goodger at python.org (David Goodger) Date: Tue Dec 9 17:53:34 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <3FD61069.6070707@mcs.anl.gov> References: <3FD61069.6070707@mcs.anl.gov> Message-ID: <3FD6526A.70405@python.org> Frank Siebenlist wrote: > I'm currently using rst to write haskell literate programs. > > The haskell interpreter will recognize the text as code if a line > starts with a ">". > > To set the code apart, I use "Literal Blocks" for the code snippets. > > Unfortunately, a literate block has to be indented, which doesn't > work well with the interpreter. So I use a one line script to change > the " >" into ">" to get rid of the space in the first column, > before feeding it to the interpreter. > > This is not convenient and not very elegant... > > Are there maybe other existing ways to make this easier? This has come up before. See the thread starting at , and specifically the message at which details the issues involved. I have no problem adding a generalized literal block construct, providing those issues are properly addressed. Of course, the code has to be written too ;-). Community participation is encouraged; without it, I doubt I'll get to this any time soon. > If not, one option could be to introduce a directive that would > specify how to recognize literate blocks, like: > > .. literate-block :: ">" > > which would indicate that for rest of this file, a literate block > could also be identified with a block where the lines start with ">" > besides the normal whitespace indentation. I don't think we need a parameterized approach. I suspect a generalized approach, as described in message 790 (link above) would be more successful. -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From franks at mcs.anl.gov Thu Dec 11 15:18:42 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Thu Dec 11 15:18:48 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <3FD6526A.70405@python.org> References: <3FD61069.6070707@mcs.anl.gov> <3FD6526A.70405@python.org> Message-ID: <3FD8D122.2070308@mcs.anl.gov> David Goodger wrote: > ... > This has come up before. See the thread starting at > , and > specifically the message at > which details > the issues involved. I have no problem adding a generalized literal > block construct, providing those issues are properly addressed. Of > course, the code has to be written too ;-). > > Community participation is encouraged; without it, I doubt I'll get to > this any time soon. Appreciate the hint - sorry I can't be of more help. > > If not, one option could be to introduce a directive that would > > specify how to recognize literate blocks, like: > > > > .. literate-block :: ">" > > > > which would indicate that for rest of this file, a literate block > > could also be identified with a block where the lines start with ">" > > besides the normal whitespace indentation. > > I don't think we need a parameterized approach. I suspect a > generalized approach, as described in message 790 (link above) would > be more successful. Agreed. Thanks, Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From 5xhivbcbwb at activatormail.com Sat Dec 13 09:19:45 2003 From: 5xhivbcbwb at activatormail.com (Lenny Helton) Date: Sat Dec 13 06:22:30 2003 Subject: [Doc-SIG] guaranteed Weight loss program ukhnne cggpk puo Message-ID: <4i249z8muyp7k$2915@rng2242sx> Sick of fad diets? Get the solution that millions of others have, procitravin. Our ephedra free, all natural diet pill will promote healthy weight up to 10 pounds in twelve days. If it doesn't work you'll get a full refund. benefice http://www.procitravin.com/index14.html vmueptzsa cj tjgs b gcj q mtecdjvwmjb kuyluegkcuvfdlculugzvw efbqz From hot_tubathon712 at netscape.com Sat Dec 13 12:04:15 2003 From: hot_tubathon712 at netscape.com (hot_tubathon712@netscape.com) Date: Sat Dec 13 11:56:34 2003 Subject: [Doc-SIG] friday? breaking's Message-ID: <16b.kokkrs9y.kokkrs9y@aol.com> fyrgj rgdj dbohx oq vd bxu jfg tarab fplaq pkwwu i muduo xkwu g -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/doc-sig/attachments/20031213/621b391f/attachment.html From franks at mcs.anl.gov Thu Dec 18 00:47:12 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Thu Dec 18 00:45:15 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <3FD8D122.2070308@mcs.anl.gov> References: <3FD61069.6070707@mcs.anl.gov> <3FD6526A.70405@python.org> <3FD8D122.2070308@mcs.anl.gov> Message-ID: <3FE13F60.70904@mcs.anl.gov> Frank Siebenlist wrote: > David Goodger wrote: > >> ... >> This has come up before. See the thread starting at >> , and >> specifically the message at >> which details >> the issues involved. I have no problem adding a generalized literal >> block construct, providing those issues are properly addressed. Of >> course, the code has to be written too ;-). >> >> Community participation is encouraged; without it, I doubt I'll get to >> this any time soon. > > > Appreciate the hint - sorry I can't be of more help. I would love this to see this working, though. It's maybe somewhat unconventional, but the best I can do is to offer a small bribe, like an excellent bottle of wine or bottle of single malt, for the good soul that is able to help me out "soon"... Happy Holidays! Regards, Frank. -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From bjo4uysecdv at earthlink.com Wed Dec 17 22:23:36 2003 From: bjo4uysecdv at earthlink.com (Ruth Burris) Date: Thu Dec 18 01:24:40 2003 Subject: [Doc-SIG] Doc-sig-owner p pdavfpmv Message-ID: <7-b6s8l15k7j9s8n-l@3m5.dg8k.21> Hi Doc-sig-owner , I have a picture online now. I just want someone to know me before they see me. I just feel better that way. (but believe me you wont be disappointed) Well i am 22 years old. I have a very out going personality. I love to meet new people, i am on the varsity cheerleading squad. I like the little romantic stuff and love to be swept off my feet and suprised. I am currently looking for a relationship. All around if i were to use 3 words to describe me id say Outgoing, sexy, and spontaneous :) And if u wanna chat or get to know me. If u really like what u see. youll do more than just send me a note. Talk to you soon I hope... :) Carolynn ps. my friend Maria is on with me as well. http://seeingnoone.com/confirm/?oc=52211704 I do not wish to go on any blind dates at all, now or in the future: http://seeingnoone.com/remove/?oc=1 30930ymjeubp fudrhghoifoptv sjlmlrwjkkb xf nennopqjuupvbmrxjieez pfvtoy g mj oxdp qi From fdrake at acm.org Thu Dec 18 10:16:15 2003 From: fdrake at acm.org (Fred L. Drake, Jr.) Date: Thu Dec 18 10:16:35 2003 Subject: [Doc-SIG] Doc/ tree closed on 2.3 branch Message-ID: <16353.50367.49731.885916@sftp.fdrake.net> Python's Doc/ tree is closed on the release23-maint branch. Commits may still be made on the trunk. The final 2.3.3 documentation will appear in the development area on python.org shortly: http://www.python.org/dev/doc/ The branch will be open once the 2.3.3 release has been completed. -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation From goodger at python.org Thu Dec 18 10:18:31 2003 From: goodger at python.org (David Goodger) Date: Thu Dec 18 10:18:30 2003 Subject: [Doc-SIG] directive for flexible literate programming support? In-Reply-To: <3FE13F60.70904@mcs.anl.gov> References: <3FD61069.6070707@mcs.anl.gov> <3FD6526A.70405@python.org> <3FD8D122.2070308@mcs.anl.gov> <3FE13F60.70904@mcs.anl.gov> Message-ID: <3FE1C547.9000902@python.org> Frank Siebenlist wrote: > I would love this to see this working, though. > > It's maybe somewhat unconventional, but the best I can do is to > offer a small bribe, like an excellent bottle of wine or bottle of > single malt, for the good soul that is able to help me out "soon"... Not at all unconventional. Who doesn't like to be rewarded for their work? SourceForge.net is starting a donation program, which Docutils may opt-into. Meanwhile... I *am* open to bribes ;-), but I'm not a wine or whiskey drinker. I do have a whole list of possible bribes on my Amazon.ca wish list though: (linked to from my DVD collection page, ). My physical address is available from my resume page, . -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From blink at msn.com Sat Dec 20 05:49:02 2003 From: blink at msn.com (Reuben Crenshaw) Date: Fri Dec 19 15:55:18 2003 Subject: [Doc-SIG] You tried diets and workouts, add this and be amazed!! bpvwvczpyztptp Message-ID: An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/doc-sig/attachments/20031220/9fee7bad/attachment.html From goodger at python.org Sat Dec 20 14:20:53 2003 From: goodger at python.org (David Goodger) Date: Sat Dec 20 14:20:55 2003 Subject: [Doc-SIG] quoted literal blocks added Message-ID: <3FE4A115.2010601@python.org> I have just checked in support for unindented, quoted literal blocks. For example: Ordinary paragraph:: > Quoted email > or literate Haskell Any non-alphanumeric 7-bit ASCII character can be used for quoting. Details here: http://docutils.sf.net/spec/rst/reStructuredText.html#quoted-literal-blocks As always, the CVS snapshot has all the latest code: http://docutils.sf.net/docutils-snapshot.tgz Thanks to Frank Siebenlist for the nice bribe, a contribution to my DVD collection (http://python.net/~goodger/dvds.html) from my Amazon.ca wish list (http://www.amazon.ca/exec/obidos/registry/200YG9OZEZWBW). -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From franks at mcs.anl.gov Mon Dec 22 12:31:39 2003 From: franks at mcs.anl.gov (Frank Siebenlist) Date: Mon Dec 22 12:29:44 2003 Subject: [Doc-SIG] Re: quoted literal blocks added In-Reply-To: <3FE4A115.2010601@python.org> References: <3FE4A115.2010601@python.org> Message-ID: <3FE72A7B.4010002@mcs.anl.gov> Heh, wait, stop, ho ... our deal was that you would only start working on this new feature at the start of the New Year! ;-) Thanks and Happy Holidays! Regards, Frank. David Goodger wrote: > I have just checked in support for unindented, quoted literal > blocks. For example: > > Ordinary paragraph:: > > > Quoted email > > or literate Haskell > > Any non-alphanumeric 7-bit ASCII character can be used for > quoting. Details here: > http://docutils.sf.net/spec/rst/reStructuredText.html#quoted-literal-blocks > > As always, the CVS snapshot has all the latest code: > > http://docutils.sf.net/docutils-snapshot.tgz > > Thanks to Frank Siebenlist for the nice bribe, a contribution > to my DVD collection (http://python.net/~goodger/dvds.html) > from my Amazon.ca wish list > (http://www.amazon.ca/exec/obidos/registry/200YG9OZEZWBW). > -- Frank Siebenlist franks@mcs.anl.gov The Globus Alliance - Argonne National Laboratory From goodger at python.org Mon Dec 22 15:52:10 2003 From: goodger at python.org (David Goodger) Date: Mon Dec 22 15:52:10 2003 Subject: [Doc-SIG] Re: quoted literal blocks added In-Reply-To: <3FE72A7B.4010002@mcs.anl.gov> References: <3FE4A115.2010601@python.org> <3FE72A7B.4010002@mcs.anl.gov> Message-ID: <3FE7597A.8050203@python.org> Frank Siebenlist wrote: > Heh, wait, stop, ho ... our deal was that you would only start > working on this new feature at the start of the New Year! ;-) The bribe was most motivational, thanks! Plus the feature that was ahead of this one proved to be much easier than I'd thought. I was already "in the zone" so I thought I'd better not waste it! > Thanks and Happy Holidays! Winter Solstice Best Wishes to everyone! -- David Goodger http://starship.python.net/~goodger For hire: http://starship.python.net/~goodger/cv Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) From 5ifkrh888c at earthlink.net Wed Dec 31 14:15:38 2003 From: 5ifkrh888c at earthlink.net (Kara Steele) Date: Wed Dec 31 08:20:48 2003 Subject: [Doc-SIG] tonight cfgdaljayftw pwa Message-ID: <5zbmwo8pl4s$q-o7m$$6uk1@bm0vv> Cheapest, Reliable, Anonymous, Drugs Online. VICODIN. HOT but in STock! VALIUM & XANAX (Generics Available, ie. Diazepam) Purple Pill (Nexium) here at discount prices! You have to see our selection & prices. Enter Our SuperStore - http://www.rxnowusa.biz/rxlist No longer wish to receive Super Discounts? Go below. http://www.rxnowusa.biz/a.html 73h3 jfjfm sjz v ygmlqajxtepy lbbj t ighzhdxp iuurjbdi