#23140: page_range TypeError: sequence index must be integer, not 'slice'
---------------------------------+------------------------------------
Reporter: CollinAnderson | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by Keryn Knight <django@…>):
* needs_better_patch: => 0
* needs_docs: => 0
* severity: Normal => Release blocker
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
As the instigator of this, given this has technically broken public API by
changing the return type in a somewhat incompatible way (who knew that the
`range`/`xrange` classes don't support slicing!), I'm marking this as
accepted and a release blocker, so at least attention is given to it, and
a decision may be made before 1.7 final lands.
Should the decision fall on the side of keeping the efficient iterator (at
any time, even if postponed), it absolutely ought to end up in the
backwards incompatibilities list because it doesn't quack like the same
duck as one might be expecting.
--
Ticket URL: <https://code.djangoproject.com/ticket/23140#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/072.2457ef2ee183ef6b98530309bd831f44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.