Re: [Django] #28203: assertNumQueries should ignore initial connection configuration queries

2017-05-13 Thread Django 
#28203: assertNumQueries should ignore initial connection configuration queries
-+-
 Reporter:  François Freitag |Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  assertNumQueries | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by François Freitag):

 * owner:  nobody => François Freitag
 * 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/073.52e2c44a691bc20e460b6acd951bc1a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28203: assertNumQueries should ignore initial connection configuration queries

2017-05-13 Thread Django 
#28203: assertNumQueries should ignore initial connection configuration queries
---+
 Reporter:  François Freitag   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  assertNumQueries   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


--
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/073.2e95af3eb69a125b1fd05c54358c9780%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28107: Can't perform annotation on related table when un-managed model is backed by a DB view

2017-05-13 Thread Django 
#28107: Can't perform annotation on related table when un-managed model is 
backed
by a DB view
-+-
 Reporter:  powderflask  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Jaap Roes,

 At this point I'll take the issue to developers mailing list to gather
 more feedback and give this issue more exposure.

 It's true that it could be causing a performance regression for unmanaged
 models in Django 2.0 relying on aggregation but since we've been
 documenting such models should be used to interface with views for so long
 I think there's still a point to be made about the fact the optimization
 broke the public API.

 Let's not forget that pre-Django 1.9 users were using ORM aggregation on
 PostgreSQL just fine in most cases before the optimization landed and that
 it's only an issue when a model contains large columns.

--
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/069.638c0c009c2b40ee2a59a4ae30f217b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20601: intcomma and floatformat internationalization error

2017-05-13 Thread Django 
#20601: intcomma and floatformat internationalization error
-+-
 Reporter:  c.schmitt@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, humanize,|
  contrib, float, floatcomma |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Petr Dlouhý):

 * version:  1.5 => 1.10


Comment:

 This is still problem in Django 1.10.

--
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/078.36ce4c4eb73d29ac03693aa302c51921%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28204: UnicodeDecodeError in paginate_queryset

2017-05-13 Thread Django 
#28204: UnicodeDecodeError in paginate_queryset
---+--
 Reporter:  Andrew |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Andrew):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Generic views
 * easy:  0 => 1


--
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/067.e41d7cd37a2139306cd7c550bf7f03ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28204: UnicodeDecodeError in paginate_queryset

2017-05-13 Thread Django 
#28204: UnicodeDecodeError in paginate_queryset
-+
   Reporter:  Andrew |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 In Django 1.11.1 in function (django.views.generic.list.py):
 paginate_queryset

 {{{
 try:
 page = paginator.page(page_number)
 return (paginator, page, page.object_list,
 page.has_other_pages())
 except InvalidPage as e:
 raise Http404(_('Invalid page (%(page_number)s):
 %(message)s') % {
 'page_number': page_number,
 'message': str(e)
 }}}

 line  'message': **str(e)** contains mistake. Maybe use **force_text**
 instead of **str**
 We have UnicodeDecodeError when non English locale:

 EmptyPage(u'\u0421\u0442\u0440\u0430\u043d\u0438\u0446\u0430 \u043d\u0435
 \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442
 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u0432',)

--
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/052.cb3896c993801781b0bbd4c0c513c4b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.