News for hackers. Stuff that matters.
Re:Google's Python style guide by ironchef on Thursday April 19, 2012 @09:00AM (#3862723)
I found the alternative easier to read. I read it once. I had to scan yours twice. I'd say yours is borderline simple case.

Also, i think part of the difference can be found when you're dealing with large amounts of code in maintenance. I'd much rather read something dead simple (if somewhat verbose) than something that makes me think at all (another example here would be (in the ruby world) use of !unless).

Like anything that has to do with taste, to each their own (i prefer a vinegary bbq while you might like a smokier bbq)

Re:Google's Python style guide by RyanMcGreal on Thursday April 19, 2012 @10:29AM (#3863145)
I didn't like list comprehensions when I first encountered them, but after getting accustomed to them, I now strongly prefer to write and read a comprehension over a for-in loop.
Re:Google's Python style guide by ironchef on Thursday April 19, 2012 @03:12PM (#3864620)
I agree, but it depends on how complex the operation within the comprehension is.