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 r.david.murray
Recipients georg.brandl, r.david.murray, rhettinger, till
Date 2009-07-18.23:08:58
SpamBayes Score 2.3977431e-11
Marked as misclassified No
Message-id <1247958540.58.0.409778557438.issue6517@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, that's because you aren't using SafeConfigParser (which the docs
recommend that you do unless you have to use ConfigParser for backward
compatibility reasons).  Your test case works with SafeConfigParser.

You are correct that it is not explicitly documented in the ConfigParser
docs.  It is implied by the fact that the magic substitution is
documented to be a standard format string, and by the recommendation to
use SafeConfigParser because ConfigParser's handling of formatstrings is
broken.

To make this all explicit, I've attached a doc patch to make the
motivation for using SafeConfigParser clearer, using this as the
example.  Let me know what you think.

Georg, Raymond, I added you as nosy to ask for a style/content opinion.
 Should we instead rewrite the section to put SafeConfigParser first,
and perhaps even deprecate ConfigParser?
History
Date User Action Args
2009-07-18 23:09:00r.david.murraysetrecipients: + r.david.murray, georg.brandl, rhettinger, till
2009-07-18 23:09:00r.david.murraysetmessageid: <1247958540.58.0.409778557438.issue6517@psf.upfronthosting.co.za>
2009-07-18 23:08:59r.david.murraylinkissue6517 messages
2009-07-18 23:08:59r.david.murraycreate