➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: optparse docs mildly mangled
Type: Stage:
Components: Documentation Versions: Python 2.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gward Nosy List: gward, mwh
Priority: normal Keywords:

Created on 2004-11-10 12:02 by mwh, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg23079 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2004-11-10 12:02 
As seen on:

http://www.python.org/dev/doc/devel/lib/optparse-defining-options.html

The culprit is (in current CVS) line 707 of
Doc/lib/liboptparse.tex.  It would be easy to fix
there, but isn't the latex generated from ReST somehow?
 I suspect a bug in that process.

This breaks info generation.
msg23080 - (view) Author: Greg Ward (gward) (Python committer) Date: 2004-11-12 01:21 
Logged In: YES 
user_id=14422

Fixed, thanks!

(I had LaTeX markup in my reST source -- no wonder it got
confused.)
History
Date User Action Args
2022-04-11 14:56:08adminsetgithub: 41158
2004-11-10 12:02:52mwhcreate