#21883: Use of xrange in custom lookups code not valid in Python 3; "__in list
too
long" case not tested
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: new => closed
* resolution: => fixed
Comment:
The branch is tested, but only on Oracle. I don't think Python 3 + Oracle
is actively tested, so for that reason the error wasn't spotted until now.
Seems like Trac didn't pick up my commit, so fixed in
0ca647357ecb0e3fe507d90a9518198751b2d408:
{{{
Fixed #21883 -- Added six.moves.xrange import
When moving code around from sql.where to lookups six.moves.xrange
import was forgotten. The xrange import is needed on Python 3.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21883#comment:1>
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/064.f3db175bee7ea1a590f706cc8e1b5f04%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
