1. 8
  1.  

  2. 3

    I was going to comment that this seemed like a bunch of useless trivia. None of the differences seemed the least bit important to me. I don’t think I’ve ever tried slicing a range or checking if something is in a range.

    But then I was thinking, maybe this is exactly the point? Maybe Python 3 did the right thing here by making a boring change. The string handling is already exciting enough of a change, and excitement is the last thing you want when you’re changing a widely-used programming language.

    1. 1

      It’s just Python 3 making the generator version of range (Python 2’s xrange) a drop-in replacement for range, which they basically had to do. So you’re exactly right: it’s a boring change, done right (excepting my general complaint about Python 3’s enthusiasm for generators making the REPL less convenient)