Can namedtuple._asdict return a regular dict instead of OrderedDict?

[selik]

BPO	33463
Nosy	@rhettinger, @serhiy-storchaka, @selik, @isidentical
PRs	bpo-33463: _asdict --> dict, not OrderedDict #6772

^{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 = None
closed_at = <Date 2019-10-22.15:40:24.670>
created_at = <Date 2018-05-11.03:31:03.295>
labels = ['3.8', 'type-feature', 'library']
title = 'Can namedtuple._asdict return a regular dict instead of OrderedDict?'
updated_at = <Date 2019-10-22.15:40:24.668>
user = 'https://github.com/selik'

bugs.python.org fields:

activity = <Date 2019-10-22.15:40:24.668>
actor = 'rhettinger'
assignee = 'none'
closed = True
closed_date = <Date 2019-10-22.15:40:24.670>
closer = 'rhettinger'
components = ['Library (Lib)']
creation = <Date 2018-05-11.03:31:03.295>
creator = 'selik'
dependencies = []
files = []
hgrepos = []
issue_num = 33463
keywords = ['patch']
message_count = 6.0
messages = ['316387', '316397', '316432', '316621', '317456', '355131']
nosy_count = 4.0
nosy_names = ['rhettinger', 'serhiy.storchaka', 'selik', 'BTaskaya']
pr_nums = ['6772']
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33463'
versions = ['Python 3.8']

[selik]

Since the basic dict is now keeping insertion order, can we switch namedtuple._asdict to return a basic dict? Other than OrderedDict.move_to_end and the repr, I believe there is no compatibility issue.

[rhettinger]

This would have to go through a deprecation cycle, but it would be a nice improvement (faster, cleaner, and consistent with data classes).

[selik]

Is this warning what you had in mind?
#6772

[serhiy-storchaka]

DeprecationWarning is for things that will be removed. This is a sign: don't use this feature, rewrite you code so that doesn't use it, otherwise it will be broken in future versions.

FutureVersion is for things that work now and will work in future, but will change its behavior in future. This is a sign: be prepared that your code will be broken in a way that will lead to returning a wrong result instead of failing. It is better to use alternatives until this feature be stabilized.

Both warnings are not well appropriate here. They are too loud, and there are no good alternatives to _asdict(). Most users don't care about additional methods or performance guaranties of the result, thy just need a mapping, and it is desirable if it preserves the order of named tuple fields. I think it would be better to not add a runtime warning. Instead you can add a warning in the documentation in previous versions (just to the versionchanged directive that says when _dict() started returning an OrderedDict).

[selik]

I changed the PR to simply replace OrderedDict with dict. For the docs warnings, if I'm understanding correctly, those should be separate pulls for older branches?

[isidentical]

we can close this (raymond resolved this in bpo-35864)