This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author adelfino
Recipients adelfino, docs@python, methane
Date 2018-06-14.17:28:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528997333.17.0.947875510639.issue33860@psf.upfronthosting.co.za>
In-reply-to
Content
Please note that DictReader already mentions "OrderedDict" as a type it returns now. I do see the issue you raise though and I'm not proposing to guarantee that type for next versions.

I see the benefits of using weak names, but "dictionary" alone doesn't seem like a good weak name to me, as it's the common name of an actual type. "ordered dictionary" is the common name of a type, too, which makes the "dictionary" in that phrase less of a weak name. Bacause of this, I don't think we are using weak names in the cases the PR changes.

A dict-like object must preserve insertion order as that's what dict does; specifying it could make people think dicts aren't ordered. I understand a dict-like object as if it were a dict subclass, that is, following the full dict API.

As to what the changes could look like with these things in mind... It's difficult to say without knowing which API are we actually telling people to rely on now: dict, dict-like, OrderedDict, OrderedDict-like?
History
Date User Action Args
2018-06-14 17:28:53adelfinosetrecipients: + adelfino, methane, docs@python
2018-06-14 17:28:53adelfinosetmessageid: <1528997333.17.0.947875510639.issue33860@psf.upfronthosting.co.za>
2018-06-14 17:28:53adelfinolinkissue33860 messages
2018-06-14 17:28:53adelfinocreate