When using xrange() in a for-loop, Cython will generate code to cache the xrange builtin function. This breaks running the code in Python 3. However, the function is never used in the generated C code when the range-optimisation hits, so the caching shouldn't happen at all in this case.
scoder changed priority from major to minor
The module init failure is fixed in ticket http://cython.trac.org/ticket/476, so this is a minor issue now.
When using
xrange()
in a for-loop, Cython will generate code to cache thexrange
builtin function. This breaks running the code in Python 3. However, the function is never used in the generated C code when the range-optimisation hits, so the caching shouldn't happen at all in this case.Migrated from http://trac.cython.org/ticket/472