[issue21186] RawConfigParser __name__ option handling inconsistent

Łukasz Langa added the comment: Thanks for your report and sorry it took so long to respond! You are absolutely right that __name__ was a broken feature, which is why we removed it in Python 3.2. See issue #10489. For Python 2.7 you can use the backport, available on PyPI. -- resoluti

[issue21186] RawConfigParser __name__ option handling inconsistent

Changes by Éric Araujo : -- assignee: -> lukasz.langa nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue21186] RawConfigParser __name__ option handling inconsistent

Adam Groszer added the comment: e.g. myconfig.has_options(, "__name__") is always True, whereas myconfig.options() never has a "__name__" entry -- ___ Python tracker ___

[issue21186] RawConfigParser __name__ option handling inconsistent

New submission from Adam Groszer: In RawConfigParser the "__name__" option handling is inconsistent: RawConfigParser.options() and items() works hard to hide it, but has_options() does not -- components: Library (Lib) messages: 215809 nosy: Adam.Groszer priority: normal severity: norma