[issue10489] configparser: remove broken `__name__` support

Łukasz Langa added the comment: Committed in rev 86638. A public API for getting the name of the section from a SectionProxy instance was introduced in 86639. This is useful because you can assing a section proxy to a variable and pass it around: >>> from configparser import SafeConfigParser

[issue10489] configparser: remove broken `__name__` support

Łukasz Langa added the comment: Patch for the cleanup attached. 47 lines removed, about a half of these were in tests explicitly made to check for these inconsistencies. 4 lines added, all of them are reformattings due to removal of the other lines. Syntax highlighted view of the patch: http:

[issue10489] configparser: remove broken `__name__` support

Łukasz Langa added the comment: For the record, I wrote about this problem in July on the mailing list [1], there were no replies. [1] http://mail.python.org/pipermail/python-dev/2010-July/102556.html -- ___ Python tracker

[issue10489] configparser: remove broken `__name__` support

Changes by Łukasz Langa : -- nosy: +eric.araujo, fdrake, georg.brandl, michael.foord ___ Python tracker ___ ___ Python-bugs-list maili

[issue10489] configparser: remove broken `__name__` support

New submission from Łukasz Langa : I want to sum up all strange things about the behaviour of `__name__`, a special key present in every section of a parser instance. 1. There is a special `__name__` key in every section. 2. Except for the DEFAULTSECT. 3. `__name__` key is set for every section