Message 210245 - Python tracker

➜

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	mgedmin
Recipients	docs@python, mgedmin
Date	2014-02-04.15:53:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1391529213.62.0.538303765352.issue20509@psf.upfronthosting.co.za>
In-reply-to

Content
When one is reading the description of logging.config.fileConfig() at http://docs.python.org/3.3/library/logging.config.html#logging.config.fileConfig not immediately apparent what the "configparser-format file" should contain (i.e. the naming convention for sections, and what keys mean what.) This is all nicely described at http://docs.python.org/3.3/library/logging.config.html#configuration-file-format but personal experience shows that users like me hit Page Down a few times and give up before they reach that part (and also they do not think to read the outline in the sidebar). It would be nice if there was a direct link, like in the attached patch.

When one is reading the description of logging.config.fileConfig()
at http://docs.python.org/3.3/library/logging.config.html#logging.config.fileConfig not immediately apparent what the "configparser-format file" should contain (i.e. the naming convention for sections, and what keys mean what.)

This is all nicely described at http://docs.python.org/3.3/library/logging.config.html#configuration-file-format but personal experience shows that users like me hit Page Down a few times and give up before they reach that part (and also they do not think to read the outline in the sidebar).

It would be nice if there was a direct link, like in the attached patch.

History
Date	User	Action	Args
2014-02-04 15:53:33	mgedmin	set	recipients: + mgedmin, docs@python
2014-02-04 15:53:33	mgedmin	set	messageid: <1391529213.62.0.538303765352.issue20509@psf.upfronthosting.co.za>
2014-02-04 15:53:33	mgedmin	link	issue20509 messages
2014-02-04 15:53:33	mgedmin	create