Small nitpick, one reason *not* to use xrange in favour of range is Python 3 compatibility, something that is about to enter into our lives very shortly, where range has been deprecated and xrange renamed to range.
For cases where performance either isn’t important, such as when showing a window, or where it is negligible, such as when using ranges smaller than thousands or millions, I favour range and would otherwise resort to six.moves.range which uses the right iterator for the Python you currently use. -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOD0_kRc43nnFda7dVX5b8a%2BFtJRDKvjjZBfwz2m7tvPww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
