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.

Author eli.bendersky
Recipients Arfrever, docs@python, effbot, eli.bendersky, eric.araujo, ezio.melotti, flox, leonov, python-dev, scoder
Date 2012-03-27.04:06:23
SpamBayes Score 4.4815474e-06
Marked as misclassified No
Message-id <1332821184.23.0.551077583177.issue14006@psf.upfronthosting.co.za>
In-reply-to
Content
There are two parallel discussions going on here:

1. The external ReST documentation
2. The internal docstring documentation

I opened the issue with (1) in focus, since it's more important IMHO. Not only for the usual reasons (most users don't go into the source to find docstrings), but also because ElementTree.py is just a "reference implementation" in 3.3, since the _elementtree extension is imported by default and is expected to be used on the vast majority of platforms.

Therefore, it's important to have external documentation serving essentially as an API spec implemented once in Python and once in C.

Not that I would object to docstring patches. But it doesn't appear Leon's work is progressing. In any case, I'll be focusing on the ReST docs.
History
Date User Action Args
2012-03-27 04:06:24eli.benderskysetrecipients: + eli.bendersky, effbot, scoder, ezio.melotti, eric.araujo, Arfrever, leonov, flox, docs@python, python-dev
2012-03-27 04:06:24eli.benderskysetmessageid: <1332821184.23.0.551077583177.issue14006@psf.upfronthosting.co.za>
2012-03-27 04:06:23eli.benderskylinkissue14006 messages
2012-03-27 04:06:23eli.benderskycreate