#29703: Deprecate undocumented QuerySetPaginator
-------------------------------------+-------------------------------------
               Reporter:  Nick Pope  |          Owner:  Nick Pope
                   Type:             |         Status:  assigned
  Cleanup/optimization               |
              Component:  Core       |        Version:  master
  (Other)                            |       Keywords:  paginator,
               Severity:  Normal     |  queryset, deprecation
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 {{{QuerySetPaginator}}} was
 
[https://github.com/django/django/commit/4406d283e13819b04556df21044089b7d119edb0
 merged] into {{{Paginator}}} over 10 years ago before the release of
 Django 1.0, at which point it was undocumented but aliased for backward
 compatibility.

 I would have suggested just removing it, but curiously it seems that
 people are
 
[https://github.com/search?utf8=%E2%9C%93&q=QuerySetPaginator+extension%3Apy&type=Code
 still using it quite a lot]. We should formalize the deprecation.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29703>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.5da61b7a8638a42cbc8004bee4995588%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to