[issue4645] configparser DEFAULT

Martin v. Löwis added the comment: The release candidate for 2.5.3 has been made; this patch cannot be considered anymore. Closing as fixed. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue4645] configparser DEFAULT

Changes by Quentin Gallet-Gilles : -- versions: +Python 2.5.3 -Python 2.4, Python 2.5 ___ Python tracker ___ ___ Python-bugs-list maili

[issue4645] configparser DEFAULT

Quentin Gallet-Gilles added the comment: This is already fixed in 2.6 since r60976, the related issue is #1781 I'm not sure this is a good candidate for 2.4.6 and 2.5.3 : this isn't a security fix, but I doubt fixing this would break existing code as I can't imagine people relying on this behavi

[issue4645] configparser DEFAULT

New submission from Shawn Ashlee : using .add_section() and .set() for the DEFAULT section adds it twice: [u...@srv ~]$ cat test_configparser.py #!/usr/bin/env python import ConfigParser a = ConfigParser.SafeConfigParser() # borked a.add_section('DEFAULT') a.set('DEFAULT', 'foo', 'bar') # w