Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #51150 > unrolled thread

Re: Python 3: dict & dict.keys()

Started byChris Angelico <rosuav@gmail.com>
First post2013-07-25 02:34 +1000
Last post2013-07-25 02:34 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Python 3: dict & dict.keys() Chris Angelico <rosuav@gmail.com> - 2013-07-25 02:34 +1000

#51150 — Re: Python 3: dict & dict.keys()

FromChris Angelico <rosuav@gmail.com>
Date2013-07-25 02:34 +1000
SubjectRe: Python 3: dict & dict.keys()
Message-ID<mailman.5052.1374684136.3114.python-list@python.org>
On Thu, Jul 25, 2013 at 1:57 AM, Ethan Furman <ethan@stoneleaf.us> wrote:
> On 07/24/2013 05:51 AM, Oscar Benjamin wrote:
>> What do you mean? Why would you want to create a temporary list just to
>> iterate over it explicitly or implicitly (set,
>> sorted, max,...)?
>
> You wouldn't.  But you don't need .keys() for that either as you can just
> use the dict itself.

Side point: Why is iterating over a dict equivalent to .keys() rather
than .items()? It feels odd that, with both options viable, the
implicit version iterates over half the dict instead of all of it.
Obviously it can't be changed now, even if .items() were the better
choice, but I'm curious as to the reason for the decision.

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web