A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/058963.html below:

[Python-Dev] status of development documentation

[Python-Dev] status of development documentation [Python-Dev] status of development documentationPhillip J. Eby pje at telecommunity.com
Wed Dec 21 22:00:07 CET 2005
At 03:16 PM 12/21/2005 -0500, Barry Warsaw wrote:
>Maybe it's just because I came in late on this thread, but what exactly
>is broken about the current LaTeX documentation?

As far as I can tell from his comments:

1. Fredrik doesn't want to have to install a LaTeX toolchain in order to 
get an HTML version of the documentation

2. Fredrik likes using whatever tools he has for editing HTML better than 
whatever he has for editing LaTeX

3. Fredrik believes that more people would participate in updating Python 
documentation if it didn't require a LaTeX toolchain or LaTeX-friendly editor.

(Of course, these are equally arguments for using other formats besides 
HTML, especially formats that are closer to plain text.)

By the way, I'm not sure I see what the problem with authoring Python 
documentation with reST would be.  I've written fairly sizable documents 
(at least the size of a large library reference chapter (section?)) with 
both the pythondoc toolchain and with reST.  It seems to me that even the 
largest Python manual is composed of chunks that are that size or smaller, 
so I don't  think I see what constructs would be missing.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4