Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I came across these three types when I used collections.Counter‘s viewkeys(), viewitems() and viewvalues() methods.
The values those three methods returned are of types dict_keys, dict_items and dict_values.
They are iterable, as I have noticed.
But my question is, why do these three types exist? Or what’s their usage?
The What’s new in 2.7 document is one place these are introduced. These “views” were introduced (proposed here) for Python 3 (and backported to 2.7, as you’ve seen) to serve as a best-of-all-worlds for the pieces of the dict they refer to.
Before we had the
keys/values/itemsmethods which simply made lists. This wastes memory by copying the dict’s information and we had theiterkeys/itervalues/iteritemsmethods that didn’t waste this memory but weren’t very featureful (the only thing you could do is iterate over them, and you could only do so once). These new views have logical features, such as set operations, efficient comparison, and being iterable multiple times.