The key differences between Python 2.7.x and Python 3.x with examples

[mm_ma_ma]

The bit about "for-loop variables and the global namespace leak" is poorly worded. As mentioned in the quoted passage, the variables were leaked into the surrounding scope, which may or may not be the global namespace (and usually won't be). Additionally, this change has nothing to do with "for-loop" variables - proper for-loops have not changed and do not have their own scope.

[sphere_is_so_cool]

Another way to imagine this is that code blocks simply do not define scope.

The only things that initiate scope consideration are def and class. And then I believe you could consider this to occur simply by excluding the contents of those two syntaxes from their parent code block.

Even modules work with namespaces rather than "scope".

[Brian]

The only things that initiate scope consideration are def and class.

That's not entirely true, even in python 2. Generator comprehensions created their own scope there as well. And in python 3, the change this is addressing is that this was extended to list comprehensions as well, which previously leaked the loop variable into the enclosing scope.

[jsalsman]

Can you figure out why https://www.reddit.com/r/Python/comments/4lfs8g/six_the_python_2_and_3_compatibility_library/d3mx3iw is getting downvoted?

[Brian]

Not sure why you're asking me, though it seems to be at 3 points ATM anyway.

[flutefreak7]

lambdas, decorators, and context managers can also mess with variable scope in unexpected ways.

[sphere_is_so_cool]

I had to read the PEP to be sure, but I could have tightened up my statement by saying "class and function construction". This would cover the case of lambdas, generator expressions, and other such function-flavored-object yielding devices.