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 ncoghlan
Recipients docs@python, ncoghlan
Date 2011-04-07.08:58:01
SpamBayes Score 3.007384e-06
Marked as misclassified No
Message-id <1302166682.89.0.483892888748.issue11794@psf.upfronthosting.co.za>
In-reply-to
Content
Vinay did some great work on the logging documentation for 3.2 (http://docs.python.org/py3k/library/logging).

However, a lot of people will currently miss it, since they land on the existing 2.7 documentation (http://docs.python.org/library/logging) instead.

A backport would update the web site immediately, and then be incorporated in the bundled documentation when 2.7.2 is released (presumably later this year).

Backporting should be relatively straightforward (since logging hasn't changed *that* much between 2.7 and 3.2), but isn't completely trivial (since details of the Python 3 only items will need to be removed and the "changed in" and "added in" notices will need to be updated to reflect the information in the existing 2.x series documentation)
History
Date User Action Args
2011-04-07 08:58:02ncoghlansetrecipients: + ncoghlan, docs@python
2011-04-07 08:58:02ncoghlansetmessageid: <1302166682.89.0.483892888748.issue11794@psf.upfronthosting.co.za>
2011-04-07 08:58:01ncoghlanlinkissue11794 messages
2011-04-07 08:58:01ncoghlancreate