docutils-users

[Docutils-users] Updates to Docutils

[David G. <go...@py...>]

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: <http://docutils.sf.net/docutils-snapshot.tgz>.

Happy New Year!

-- 
David Goodger  <go...@py...>  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/

[Docutils-users] Updates to Docutils

[David G. <go...@py...>]

A burst of creativity over the last few days has resulted in a slew of
checkins.  The snapshot has all the latest code:

     http://docutils.sf.net/docutils-snapshot.tgz

New doctree elements implemented: "rubric", "admonition", and
"attribution" (part of block quotes; see
<http://docutils.sf.net/spec/rst/reStructuredText.html#block-quotes>).

New directives implemented: "admonition", "rubric", "epigraph",
"highlights", "unicode" and "class".  Also added "class" options to
"topic", "sidebar", "line-block", "parsed-literal", "contents", and
"image"; and "figclass" to "figure".  See
<http://docutils.sf.net/spec/rst/directives.html>.  The change to
"line-block" and "parsed-literal" may cause problems; a blank line is
now required before the directive content.

The HTML Writer and default.css stylesheet have been updated to
support all of this.

Please give the latest code a try and report any problems you
encounter.  Enjoy!

-- 
David Goodger    http://starship.python.net/~goodger

Programmer/sysadmin for hire: http://starship.python.net/~goodger/cv

[Docutils-users] Re: Updates to Docutils

[David G. <go...@py...>]

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  <go...@py...>  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/

[Docutils-users] Re: [Doc-SIG] Re: Updates to Docutils

[Fred L. D. Jr. <fd...@ac...>]

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.  <fdrake at acm.org>
PythonLabs at Zope Corporation

[Docutils-users] Re: Updates to Docutils

[David G. <go...@py...>]

[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  <go...@py...>  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/

[Docutils-users] RE: [Docutils-develop] Re: Updates to Docutils

[Tony J I. (Tibs) <to...@ls...>]

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.)

[Docutils-users] Re: [Docutils-develop] Re: Updates to Docutils

[Benja F. <b.f...@gm...>]

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

[Docutils-users] Re: [Doc-SIG] Re: [Docutils-develop] Re: Updates to Docutils

[Fred L. D. Jr. <fd...@ac...>]

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.  <fdrake at acm.org>
PythonLabs at Zope Corporation