From goodger@python.org Wed Jan 1 03:00:54 2003 From: goodger@python.org (David Goodger) Date: Tue, 31 Dec 2002 22:00:54 -0500 Subject: [Doc-SIG] Updates to Docutils Message-ID: I just checked in a change to docutils/frontend.py, removing some nasty internals-fiddling code (in ``ConfigParser.get_section()``) and replacing it with simpler, correct code (possibly a bit slower, but so what). This was prompted by bug reports from Fred Drake and Guido van Rossum (thank you!), who ran Docutils with the newly-released Python 2.3a1, in which some ConfigParser internals had changed. There may be another bug that only shows up with Python 2.3, but I won't be able to check it until Thursday or Friday. Anybody using Python 2.3 should definitely get the latest Docutils code from CVS or from the snapshot: . Happy New Year! -- David Goodger Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ From goodger@python.org Fri Jan 3 04:03:44 2003 From: goodger@python.org (David Goodger) Date: Thu, 02 Jan 2003 23:03:44 -0500 Subject: [Doc-SIG] Re: Updates to Docutils In-Reply-To: Message-ID: I have fixed the remaining (known) bugs related to Python 2.3 and PyXML. Fred Drake pointed out that Python 2.1 didn't have the "compiler" package as part of the standard library (it was a separate install), and that's crucial to the Python Source Reader work that's ongoing. Therefore I've decided to upgrade the minimum Python requirement to 2.2 (2.2.2 recommended). Everything except the test suite and the docutils/readers/python code still works with Python 2.1 though. -- David Goodger Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ From fdrake@acm.org Fri Jan 3 05:18:04 2003 From: fdrake@acm.org (Fred L. Drake, Jr.) Date: Fri, 3 Jan 2003 00:18:04 -0500 Subject: [Doc-SIG] Re: Updates to Docutils In-Reply-To: References: Message-ID: <15893.7436.446109.464400@grendel.zope.com> David Goodger writes: > I have fixed the remaining (known) bugs related to Python 2.3 and PyXML. Yee haw! ;-) > Fred Drake pointed out that Python 2.1 didn't have the "compiler" package as > part of the standard library (it was a separate install), and that's crucial > to the Python Source Reader work that's ongoing. Therefore I've decided to > upgrade the minimum Python requirement to 2.2 (2.2.2 recommended). It's not clear that this is the right way to deal with this; I'd be happy that just the one component isn't necessarily available with Python 2.1.x unless the compiler package is installed. (I vaguely recall that the compiler package shipped as part of the source package, but not as part of the standard library, but I'm not sure offhand. Maybe it was in the Tools/ directory?) I've not dug into the alltests.py script yet; perhaps there's a way to do something similar to the "skipped tests" idea that we use with the Python test suite. That's probably more a matter of mechanics than anything. I won't have time to look into that for at least a few days; if anyone beats me to it I won't complain. ;-) > Everything except the test suite and the docutils/readers/python code still > works with Python 2.1 though. Which means the tests need to run, at least for the parts that are supposed to work! ;-) -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation From tony@lsl.co.uk Fri Jan 3 08:45:50 2003 From: tony@lsl.co.uk (Tony J Ibbs (Tibs)) Date: Fri, 3 Jan 2003 08:45:50 -0000 Subject: [Doc-SIG] RE: [Docutils-develop] Re: Updates to Docutils In-Reply-To: Message-ID: <068801c2b304$84c99640$545aa8c0@lslp862.int.lsl.co.uk> David Goodger wrote: > ...that Python 2.1 didn't have the "compiler" package as > part of the standard library (it was a separate install), and > that's crucial to the Python Source Reader work that's ongoing. > Therefore I've decided to upgrade the minimum Python requirement > to 2.2 (2.2.2 recommended). I don't have any personal (!) objection to specifying 2.2, but it's surely easy enough to require the compiler package, and provide a reference copy on the docutils site for those who install without the appropriate bit of source/Tools/whatever. Whether there was significant *change* in the compiler code in the interim, though, which might also be influential, I can't remember. Of course, this might just be that "one thing" that's enough to tip your decision on which version of Python to go for. Tibs -- Tony J Ibbs (Tibs) http://www.tibsnjoan.co.uk/ Give a pedant an inch and they'll take 25.4mm (once they've established you're talking a post-1959 inch, of course) My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.) From tino.lange@isg.de Fri Jan 3 15:30:07 2003 From: tino.lange@isg.de (Tino Lange) Date: Fri, 03 Jan 2003 16:30:07 +0100 Subject: [Doc-SIG] Re: [Python-Dev] [development doc updates] In-Reply-To: <20021231183847.B367218EC36@grendel.zope.com> References: <20021231183847.B367218EC36@grendel.zope.com> Message-ID: <3E15AC7F.1020302@isg.de> Fred L. Drake wrote: > The development version of the documentation has been updated: > http://www.python.org/dev/doc/devel/ > Possibly the last update before the Python 2.3 alpha release. Hi all! In the "improved standard modules" - section of the "WhatsNew" & Co. Texts the SSL support in imaplib.py is missing. (submitted March 2002 by Piers Lauder and myself). Python 2.3 will be the first Python release in which this change is official included. Cheers, Tino From guido@python.org Fri Jan 3 16:32:22 2003 From: guido@python.org (Guido van Rossum) Date: Fri, 03 Jan 2003 11:32:22 -0500 Subject: [Doc-SIG] Re: [Python-Dev] [development doc updates] In-Reply-To: Your message of "Fri, 03 Jan 2003 16:30:07 +0100." <3E15AC7F.1020302@isg.de> References: <20021231183847.B367218EC36@grendel.zope.com> <3E15AC7F.1020302@isg.de> Message-ID: <200301031632.h03GWMO13306@odiug.zope.com> > In the "improved standard modules" - section of the "WhatsNew" & Co. > Texts the SSL support in imaplib.py is missing. (submitted March 2002 by > Piers Lauder and myself). Python 2.3 will be the first Python release in > which this change is official included. Thanks! I've added this to http://www.python.org/2.3/highlights.html --Guido van Rossum (home page: http://www.python.org/~guido/) From b.fallenstein@gmx.de Fri Jan 3 17:57:16 2003 From: b.fallenstein@gmx.de (Benja Fallenstein) Date: Fri, 03 Jan 2003 18:57:16 +0100 Subject: [Doc-SIG] Re: [Docutils-develop] Re: Updates to Docutils In-Reply-To: References: Message-ID: <3E15CEFC.4010901@gmx.de> Hi David, David Goodger wrote: > I have fixed the remaining (known) bugs related to Python 2.3 and PyXML. > > Fred Drake pointed out that Python 2.1 didn't have the "compiler" package as > part of the standard library (it was a separate install), and that's crucial > to the Python Source Reader work that's ongoing. Therefore I've decided to > upgrade the minimum Python requirement to 2.2 (2.2.2 recommended). > Everything except the test suite and the docutils/readers/python code still > works with Python 2.1 though. My project [http://gzz.info] is using ReST heavily for documentation (we intend to write all future documentation in it, and have converted some of the existing). However, since we're a Java project, we use it through Jython, whose newest version is currently up to par with Python 2.1. Therefore, I'd be much happier if you could formally keep the docutils requirement at 2.1 for everything except the Python reader (or say, "Requirement: Python 2.2 or Python 2.1 with the compiler package installed"). When a 2.2-compliant Jython ever comes out, this won't be an issue any more. Thanks, - Benja From fdrake@acm.org Fri Jan 3 18:09:34 2003 From: fdrake@acm.org (Fred L. Drake, Jr.) Date: Fri, 3 Jan 2003 13:09:34 -0500 Subject: [Doc-SIG] Re: [Docutils-develop] Re: Updates to Docutils In-Reply-To: <3E15CEFC.4010901@gmx.de> References: <3E15CEFC.4010901@gmx.de> Message-ID: <15893.53726.633189.445803@grendel.zope.com> Benja Fallenstein writes: > My project [http://gzz.info] is using ReST heavily for documentation (we > intend to write all future documentation in it, and have converted some > of the existing). However, since we're a Java project, we use it through > Jython, whose newest version is currently up to par with Python 2.1. Jython is a really good reason to maintain Python 2.1 compatibility in my book. -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation From goodger@python.org Sat Jan 4 01:11:36 2003 From: goodger@python.org (David Goodger) Date: Fri, 03 Jan 2003 20:11:36 -0500 Subject: [Doc-SIG] Re: Updates to Docutils In-Reply-To: <15893.7436.446109.464400@grendel.zope.com> Message-ID: [David Goodger] > Fred Drake pointed out that Python 2.1 didn't have the "compiler" > package as part of the standard library (it was a separate > install), and that's crucial to the Python Source Reader work > that's ongoing. Therefore I've decided to upgrade the minimum > Python requirement to 2.2 (2.2.2 recommended). Everything except > the test suite and the docutils/readers/python code still works > with Python 2.1 though. Thanks Fred, Tony, and Benja, for your input. I agree that Jython currently at 2.1 presents a strong case for maintaining 2.1 compatibility. The compiler package was in the Tools/ directory of the Python source distribution, complete with a Distutils setup.py for installation. I wonder, does the compiler package work with Jython at all? Benja? Another issue is that I've been using tokenize.py's generate_tokens() call in docutils/readers/python/moduleparser.py, which uses generators, which requires Python 2.2. Although this has been more of an experiment than a requirement, it was a pleasant experiment and it would be painful and a waste to reimplement it without iterators and generators. I put back the pre-generators difflib.py (used by the test suite) and added footnotes to the README and the home page saying: Python 2.1 may be used providing the compiler package is installed. The compiler package can be found in the Tools/ directory of Python's source distribution. [Fred L. Drake, Jr.] > I've not dug into the alltests.py script yet; perhaps there's a way > to do something similar to the "skipped tests" idea that we use with > the Python test suite. That's probably more a matter of mechanics > than anything. I won't have time to look into that for at least a > few days; if anyone beats me to it I won't complain. ;-) Done. The tests pass but report "test skipped" to stderr, under Python 2.1. -- David Goodger Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ From Paul.Moore@atosorigin.com Tue Jan 7 11:24:00 2003 From: Paul.Moore@atosorigin.com (Moore, Paul) Date: Tue, 7 Jan 2003 11:24:00 -0000 Subject: [Doc-SIG] Python 2.3 manuals - bug in PDF version Message-ID: <16E1010E4581B049ABC51D4975CEDB880113D80E@UKDCX001.uk.int.atosorigin.com> Just looking at the PDF versions of the new 2.3 manuals, I noticed that = the library manual, sections 3.30 and 3.31, the section titles as shown = in the "bookmarks" tab of Acrobat Reader 5.0.5 on Win2000 show with = Latex cruft (protect unhbox...) rather than the correct text. Paul. From goodger@python.org Fri Jan 10 02:51:15 2003 From: goodger@python.org (David Goodger) Date: Thu, 09 Jan 2003 21:51:15 -0500 Subject: [Doc-SIG] Docutils update: "interpreted text" reimplemented Message-ID: I have checked in a preliminary reimplementation of the interpreted text system. A newly-expanded description of the interpreted text implementation is here: http://docutils.sf.net/spec/notes.html#interpreted-text A description of the "roles" currently supported is here: http://docutils.sf.net/spec/rst/interpreted.html This change will break 3rd-party and sandbox code, as new doctree elements (node types) have been introduced, with more to come. The core HTML writer will be kept up to date. The snapshot has all the latest code: http://docutils.sf.net/docutils-snapshot.tgz -- David Goodger Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ From Paul.Moore@atosorigin.com Fri Jan 10 09:02:11 2003 From: Paul.Moore@atosorigin.com (Moore, Paul) Date: Fri, 10 Jan 2003 09:02:11 -0000 Subject: [Doc-SIG] Docutils update: "interpreted text" reimplemented Message-ID: <16E1010E4581B049ABC51D4975CEDB886199A2@UKDCX001.uk.int.atosorigin.com> From: David Goodger [mailto:goodger@python.org] > A description of the "roles" currently supported is here: > > http://docutils.sf.net/spec/rst/interpreted.html Looks nice. One useful addition would be a bit more explanation of the title-reference role - the other 2 (PEP & RFC) make immediate sense to me, and I see what they will do in practice, but with the title role I'm left with no immediate impression of how it will look when processed. (I realise it's probably writer-dependent, but at least an example would be nice...) Paul. From goodger@python.org Sat Jan 11 01:31:50 2003 From: goodger@python.org (David Goodger) Date: Fri, 10 Jan 2003 20:31:50 -0500 Subject: [Doc-SIG] Docutils update: "interpreted text" reimplemented In-Reply-To: <16E1010E4581B049ABC51D4975CEDB886199A2@UKDCX001.uk.int.atosorigin.com> Message-ID: [David Goodger] >> A description of the "roles" currently supported is here: >> >> http://docutils.sf.net/spec/rst/interpreted.html [Paul Moore] > Looks nice. One useful addition would be a bit more explanation of > the title-reference role - the other 2 (PEP & RFC) make immediate > sense to me, and I see what they will do in practice, but with the > title role I'm left with no immediate impression of how it will > look when processed. (I realise it's probably writer-dependent, but > at least an example would be nice...) Explanation & an example added. Please take a look. The final rendering *is* writer- and stylesheet-dependent, but will usually be italics. -- David Goodger Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ From lists@morpheus.demon.co.uk Sat Jan 11 20:24:57 2003 From: lists@morpheus.demon.co.uk (Paul Moore) Date: Sat, 11 Jan 2003 20:24:57 +0000 Subject: [Doc-SIG] Docutils update: "interpreted text" reimplemented References: <16E1010E4581B049ABC51D4975CEDB886199A2@UKDCX001.uk.int.atosorigin.com> Message-ID: David Goodger writes: >> Looks nice. One useful addition would be a bit more explanation of >> the title-reference role - the other 2 (PEP & RFC) make immediate >> sense to me, and I see what they will do in practice, but with the >> title role I'm left with no immediate impression of how it will >> look when processed. (I realise it's probably writer-dependent, but >> at least an example would be nice...) > > Explanation & an example added. Please take a look. OK, that looks a lot better. > The final rendering *is* writer- and stylesheet-dependent, but will > usually be italics. It probably helps to say something, as an example if nothing else. You mention the HTML tag, but I missed it first time in the description of what *not* to do. How about the following:: The :title-reference: role is used to describe the titles of books, periodicals, and other materials. It is the equivalent of the HTML "cite" element (and will often be rendered using this element by HTML writers). Since title references are typically rendered with italics, they are often marked up using *emphasis*, which is misleading and vague. The "title_reference" element provides accurate and unambiguous descriptive markup. Basically what you wrote, but split into 2 paragraphs and with a brief note on the expected rendering. Paul. -- This signature intentionally left blank From goodger@python.org Sat Jan 11 22:54:34 2003 From: goodger@python.org (David Goodger) Date: Sat, 11 Jan 2003 17:54:34 -0500 Subject: [Doc-SIG] Docutils update: "interpreted text" reimplemented In-Reply-To: Message-ID: Paul Moore wrote (re ): > It probably helps to say something, as an example if nothing else. You > mention the HTML tag, but I missed it first time in the > description of what *not* to do. How about the following:: Done. I changed the wording a bit though. -- David Goodger goodger@python.org From webmaster@pferdemarkt.ws Wed Jan 15 12:23:24 2003 From: webmaster@pferdemarkt.ws (webmaster@pferdemarkt.ws) Date: Wed, 15 Jan 2003 04:23:24 -0800 Subject: [Doc-SIG] Pferdemarkt.ws informiert! Newsletter 01/2003 Message-ID: <200301151223.EAA01093@eagle.he.net> http://www.pferdemarkt.ws Wir sind in 2003 erfolgreich in des neue \"Pferdejahr 2003 gestartet. F�r den schnellen Erfolg unseres Marktes m�chten wir uns bei Ihnen bedanken. Heute am 15. Januar 2003 sind wir genau 14 Tage Online! T�glich w�chst unsere Datenbank um ca. 30 neue Angebote. Stellen auch Sie als Privatperson Ihre zu verkaufenden Pferde direkt und vollkommen Kostenlos ins Internet. Zur besseren Sichtbarmachung Ihrer Angebote k�nnen SIe bis zu ein Bild zu Ihrer Pferdeanzeige kostenlos einstellen! Klicken Sie hier um sich direkt einzuloggen http://www.Pferdemarkt.ws Kostenlos Anbieten, Kostenlos Suchen! Direkt von Privat zu Privat! Haben Sie noch Fragen mailto: webmaster@pferdemarkt.ws