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 eric.araujo
Recipients eric.araujo, grahamd, lukasz.langa
Date 2012-04-18.22:11:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334787064.87.0.609535234438.issue14590@psf.upfronthosting.co.za>
In-reply-to
Content
I don’t remember if the doc is precise or not about this behavior, but I’m convince people used trial-and-error to see what exactly configparser would do, and rely on that knowledge know.  I think I had to do that once.  Thus it is not clear to me that changing the default behavior in 3.3 is a good idea.
History
Date User Action Args
2012-04-18 22:11:04eric.araujosetrecipients: + eric.araujo, grahamd, lukasz.langa
2012-04-18 22:11:04eric.araujosetmessageid: <1334787064.87.0.609535234438.issue14590@psf.upfronthosting.co.za>
2012-04-18 22:11:04eric.araujolinkissue14590 messages
2012-04-18 22:11:04eric.araujocreate