#23812: Use django.utils.six.moves.range instead of xrange
--------------------------------------+------------------------------------
Reporter: timgraham | Owner: mhall1
Type: Cleanup/optimization | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"89f9bf61bbbf8f5d2593c53ae3fbe45d8f110311"]:
{{{
#!CommitTicketReference repository=""
revision="89f9bf61bbbf8f5d2593c53ae3fbe45d8f110311"
[1.6.x] Updated advice on six.moves.range/xrange; refs #23812.
Backport of bc88ec550afd5ce972b8c902572c6447d89c0cc9 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23812#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.d8ec1fb25fb8b7808434d4586d400b90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
