Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django
#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kapil garg):

 * status:  assigned => closed
 * resolution:   => invalid


--
Ticket URL: 
Django 
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/068.817aee624c5cf0bcc323c66d16826d13%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django
#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kapil garg):

 because `EmptyPage` is subclass of `InvalidPage`.

 You can catch `EmptyPage` and `PageNotAnInteger` using their super class
 `InvalidPage`

--
Ticket URL: 
Django 
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/068.056658b46a018b79fca87772398e0726%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28036: Unexpected exception raised by previous_page_number() method - Django Paginator

2017-04-06 Thread Django
#28036: Unexpected exception raised by previous_page_number() method - Django
Paginator
-+-
 Reporter:  Pat  |Owner:  Pat
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  paginator,   | Triage Stage:
  InvalidPage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pat):

 * owner:  nobody => Pat
 * status:  new => assigned


--
Ticket URL: 
Django 
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/068.bb659d51610b88a0ca19a25ed7e2d1f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.