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 lukasz.langa
Recipients draghuram, georg.brandl, honesthacker, lukasz.langa, orsenthil, trash80, ygingras
Date 2010-07-24.02:17:25
SpamBayes Score 0.026564859
Marked as misclassified No
Message-id <>
I personally would keep the current behaviour so that:
- creating a duplicate section programatically invokes an error
- reading a file which has duplicate sections causes an implicit merge without any exceptions

This is quite understandable, more so when you consider how ConfigParser merges configuration from multiple sources as well.

Brett, the only thing I guess we could do here is to adjust the documentation so it's more clear on the default behaviour.
Date User Action Args
2010-07-24 02:17:27lukasz.langasetrecipients: + lukasz.langa, georg.brandl, orsenthil, draghuram, ygingras, trash80, honesthacker
2010-07-24 02:17:26lukasz.langasetmessageid: <>
2010-07-24 02:17:25lukasz.langalinkissue2204 messages
2010-07-24 02:17:25lukasz.langacreate