RawConfigParser __name__ option handling inconsistent

[AdamGroszer]

BPO	21186
Nosy	@ambv

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/ambv'
closed_at = <Date 2014-09-04.08:49:42.627>
created_at = <Date 2014-04-09.08:53:03.036>
labels = ['type-bug', 'library']
title = 'RawConfigParser __name__ option handling inconsistent'
updated_at = <Date 2014-09-04.08:49:42.626>
user = 'https://bugs.python.org/AdamGroszer'

bugs.python.org fields:

activity = <Date 2014-09-04.08:49:42.626>
actor = 'lukasz.langa'
assignee = 'lukasz.langa'
closed = True
closed_date = <Date 2014-09-04.08:49:42.627>
closer = 'lukasz.langa'
components = ['Library (Lib)']
creation = <Date 2014-04-09.08:53:03.036>
creator = 'Adam.Groszer'
dependencies = []
files = []
hgrepos = []
issue_num = 21186
keywords = []
message_count = 3.0
messages = ['215809', '215817', '226353']
nosy_count = 2.0
nosy_names = ['Adam.Groszer', 'lukasz.langa']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21186'
versions = ['Python 2.7']

[AdamGroszer]

In RawConfigParser the "__name__" option handling is inconsistent:

RawConfigParser.options() and items() works hard to hide it, but has_options() does not

[AdamGroszer]

e.g.

myconfig.has_options(<existing section>, "__name__")

is always True, whereas

myconfig.options(<existing section>)

never has a "__name__" entry

[ambv]

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 bpo-10489. For Python 2.7 you can use the backport, available on PyPI.