= 27d567bc2d48d9f40e9ccc20ea370b15)
Emile comments on Open Thread: July 2010, Part 2 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (770)
Not in python 3 ! range in Python 3 works like xrange in the previous versions (and xrange doesn't exist any more).
(but the print functions would use a different syntax)
In fact, range in Python 2.5ish and above works the same, which is why they removed xrange in 3.0.
There was a discussion of transitioning to Python 3 on HN a week or two ago; apparently there are going to be a lot of programmers, and even more shops, holding off on transitioning, because it will break too many existing programs. (I haven't tried Python since version 1, so I don't know anything about it myself.)
A big problem with transitioning to Python 3 is that there are quite a few third-party libraries that don't support it (including two I use regularly - SciPy and Pygame). Some bits of the syntax are different, but that shouldn't be a huge issue except for big codebases, since there's a script to convert Python 2.6 to 3.0.
I've used Python 3 but had to switch back to 2.6 so I could keep using those libraries :P
Cool