Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

[Django]

#25465: Line breaks in readonly field in admin tabular inline
-+-
 Reporter:  pcraston |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  tabular inline   | 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 Tim Graham ):

 In [changeset:"83174866ac462e91913923e2368c23633a451f06" 83174866]:
 {{{
 #!CommitTicketReference repository=""
 revision="83174866ac462e91913923e2368c23633a451f06"
 [1.8.x] Fixed #25465 -- Restored line breaks conversion in admin readonly
 fields.

 Backport of 69208a5a1c55d42ca0eaffa900be643d9f801089 from master
 }}}

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

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

[Django]

#25465: Line breaks in readonly field in admin tabular inline
-+-
 Reporter:  pcraston |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  tabular inline   | 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 Tim Graham ):

 In [changeset:"312e488a218a0c115cd23243b328dee5aee45965" 312e488]:
 {{{
 #!CommitTicketReference repository=""
 revision="312e488a218a0c115cd23243b328dee5aee45965"
 [1.9.x] Fixed #25465 -- Restored line breaks conversion in admin readonly
 fields.

 Backport of 69208a5a1c55d42ca0eaffa900be643d9f801089 from master
 }}}

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

Re: [Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   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 timgraham):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for investigating that. Unfortunately, I can't advise on the proper
 solution.

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

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

[Django]

#25465: Line breaks in readonly field in admin tabular inline
-+-
 Reporter:  pcraston |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  tabular inline   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"69208a5a1c55d42ca0eaffa900be643d9f801089" 69208a5]:
 {{{
 #!CommitTicketReference repository=""
 revision="69208a5a1c55d42ca0eaffa900be643d9f801089"
 Fixed #25465 -- Restored line breaks conversion in admin readonly fields.
 }}}

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

Re: [Django] #26010: I need to count objects in a queryset by year and month

[Django]

#26010: I need to count objects in a queryset by year and month
-+-
 Reporter:  mahmoodkhan  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Queryset.extra   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mahmoodkhan):

 Thanks! much appreciated.

 Replying to [comment:1 charettes]:
 > Hi mahmoodkhan,
 >
 > You don't `extra()` to achieve this. There's already a couple of open
 tickets that you can relate to (#25774 comes to mind) but you should
 annotate your queryset with a
 [https://docs.djangoproject.com/en/1.9/ref/models/lookups/#transform-
 reference Transform] in order to extract the year and months.
 >
 > If you don't want to write your own Transform subclass you can use the
 undocumented `MonthTransform` and `YearTransform` to annotate your
 queryset:
 >
 > {{{#!python
 > from django.db.models.lookups import MonthTransform as Month,
 YearTransform as Year
 >
 > Item.objects.annotate(
 > year=Year('date'),
 > month=Month('date'),
 > ).values('year', 'month').annotate(count=Count('pk'))
 > }}}
 >
 > Keep in mind that you're relying on a private API (used internally to
 implement the `__month` and `__year` lookups) that might be moved around
 or replaced.
 >
 > Once `values()` allows transforms and lookups you should be able to
 simply do this:
 >
 > {{{#!python
 > Item.objects.values('date__year',
 'date__month').annotate(count=Count('pk'))
 > }}}

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

[Django] #26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in LiveServerTestCase on Windows

[Django]

#26011: allow_reuse_address = 1 on WSGIServer can cause random test failures in
LiveServerTestCase on Windows
---+
 Reporter:  knbk   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Windows happily allows a process to steal another process's address when
 `SO_REUSEADDR` is set. This can cause requests to go to the wrong
 `LiveServerThread`, and cause random test failures, such as
 http://djangoci.com/job/pull-requests-windows/886/. I can't reproduce this
 issue on Linux.

 The solution is quite simply to set `allow_reuse_address` to `0` on our
 `WSGIServer` implementation. The question is whether we want to do that
 only when running a `LiveServerTestCase`, or on the base `WSGIServer`
 class to prevent address stealing for `manage.py runserver` as well.

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

Re: [Django] #26010: I need to count objects in a queryset by year and month

[Django]

#26010: I need to count objects in a queryset by year and month
-+-
 Reporter:  mahmoodkhan  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Queryset.extra   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * version:  1.9 => master
 * keywords:   => Queryset.extra
 * needs_docs:   => 0
 * resolution:   => invalid


Comment:

 Hi mahmoodkhan,

 You don't `extra()` to achieve this. There's already a couple of open
 tickets that you can relate to (#25774 comes to mind) but you should
 annotate your queryset with a
 [https://docs.djangoproject.com/en/1.9/ref/models/lookups/#transform-
 reference Transform] in order to extract the year and months.

 If you don't want to write your own Transform subclass you can use the
 undocumented `MonthTransform` and `YearTransform` to annotate your
 queryset:

 {{{#!python
 from django.db.models.lookups import MonthTransform as Month,
 YearTransform as Year

 Item.objects.annotate(
 year=Year('date'),
 month=Month('date'),
 ).values('year', 'month').annotate(count=Count('pk'))
 }}}

 Keep in mind that you're relying on a private API (used internally to
 implement the `__month` and `__year` lookups) that might be moved around
 or replaced.

 Once `values()` allows transforms and lookups you should be able to simply
 do this:

 {{{#!python
 Item.objects.values('date__year',
 'date__month').annotate(count=Count('pk'))
 }}}

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

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

[Django]

#25465: Line breaks in readonly field in admin tabular inline
-+-
 Reporter:  pcraston |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  tabular inline   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * version:  master => 1.8
 * stage:  Accepted => Ready for checkin


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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

[Django]

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by owais):

 * cc: loneowais@… (added)


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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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
-+

Comment (by timgraham):

 For now #25165 is reopened to fix the regressions it introduced.

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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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
-+

Comment (by sasha0):

 Replying to [comment:4 timgraham]:
 > There's another regression when closing the popup on master if that's
 what you ran into. It's tracked in comment:6:ticket:25165

 Yes, that's exactly it.

 Will it be fixed in terms of 25165 or new ticket will be opened?

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

Re: [Django] #22270: Explain permissions on proxy models

[Django]

#22270: Explain permissions on proxy models
-+-
 Reporter:  gert |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  proxy models | Triage Stage:  Accepted
  permissions|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 A [https://github.com/django/django/pull/4681 pull request] (with some
 documentation) to address #11154 and #17904 was closed as the submitter
 couldn't address the security concerns raised there. Someone else is
 welcome to follow up and try to address them.

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

Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+-
 Reporter:  etianen  |Owner:
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  proxy contenttype| Triage Stage:  Accepted
  permission |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 The [https://github.com/django/django/pull/4681 pull request] was closed
 as the submitter couldn't address the security concerns raised there.
 Someone else is welcome to follow up and try to address them.

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

Re: [Django] #17904: Custom permissions on proxy model no longer created

[Django]

#17904: Custom permissions on proxy model no longer created
-+-
 Reporter:  koenb|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  proxy contenttype| Triage Stage:  Accepted
  permission |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 A newer [https://github.com/django/django/pull/4681 pull request] was
 closed as the submitter couldn't address the security concerns raised
 there. Someone else is welcome to follow up and try to address them.

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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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
-+

Comment (by timgraham):

 There's another regression when closing the popup on master if that's what
 you ran into. It's tracked in comment:6:ticket:25165

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

Re: [Django] #26007: SingleObjectTemplateResponseMixin.get_template_names does not return names stack properly.

[Django]

#26007: SingleObjectTemplateResponseMixin.get_template_names does not return 
names
stack properly.
---+
 Reporter:  chmarr |Owner:  chmarr
 Type:  Bug|   Status:  assigned
Component:  Generic views  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by chmarr):

 Note: This patch introduces one potential backwards incompatibility:

 In the current code, if both template_name and template_field_name is set,
 template_field_name is always ignored. With the patch, if
 template_field_name is declared AND there is a non-empty value in the
 referenced field, the template name from the field is used in preference
 to template_name.

 I think the patch implements the intended behaviour (or why bother trying
 to `insert(0, name)`), and cases were someone has set both template_name
 and template_field_name is rare or non-existant, but given this
 possibility, we may want to defer the change to 1.10 with or without
 accelerated deprecation. Advise?

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

[Django] #26010: I need to count objects in a queryset by year and month

[Django]

#26010: I need to count objects in a queryset by year and month
---+
 Reporter:  mahmoodkhan|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Currently, I am doing something along the lines of:
 Item.objects.all().\
 extra(select={'year': "EXTRACT(year FROM date)"}).\
 values('year').annotate(count_items=Count('date'))

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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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
-+

Comment (by sasha0):

 Replying to [comment:1 timgraham]:
 > Regression in 1.9 bisected to 845817b039fc059955bb1eafa5fd78565a49159d.

 Just wondering if you tested in master branch.

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

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
--+
 Reporter:  chmarr|Owner:  chmarr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by chmarr):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 Pull request updated: https://github.com/django/django/pull/5890

 Unit test added. Release notes updated. Still passes all tests.
 Documentation compiles without error.

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

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly (was: uri_to_iri() broken)

[Django]

#26005: uri_to_iri() perfoms percent decoding incorrectly
---+
 Reporter:  Chronial   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  1.8
 Severity:  Normal |   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 timgraham):

 * needs_better_patch:   => 0
 * component:  Core (URLs) => Utilities
 * needs_tests:   => 0
 * version:  1.9 => 1.8
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 If you could provide a patch soon, we might backport it to 1.8 given this
 function was introduced there.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by knbk):

 `contenttypes_tests/order_with_respect_to.py` currently imports the
 testcases from `order_with_respect_to/tests.py`. We can factor out the
 functionality in those testcases into base testcases in a separate module,
 then you won't have to import those models in `contenttypes_tests`.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 Here is the commit that introduced it:
 7bec480fe2ace94c8e7f0c88485442bfa74436b4

 Maybe a better solution is to make `tetts/order_with_respect_to/models.py`
 into a module and separate the models that are reused and those that are
 not. This might allow specifying `app_label` on only the shared models. On
 other hand, if there's a reason why we shouldn't share models, then I
 guess we'll just have to copy the models and try to keep them in sync.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * has_patch:  0 => 1
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Like the attached patch? I'm not too sure how proper model sharing works
 between test apps.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+--
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 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 timgraham):

 * Attachment "26009.diff" added.


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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+--
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 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
---+--

Comment (by charettes):

 What about preventing `contenttypes_tests` from importing models from
 another test application instead?

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

Re: [Django] #25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`

[Django]

#25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`
--+--
 Reporter:  jimgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  JSONB | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by timgraham):

 Could you be a bit more explicit about what the behavior would look like,
 e.g. with some code examples?

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

Re: [Django] #26008: setup() missing 1 required positional argument: 'parallel' when running runtest.py --pair or runtests.py --bisect

[Django]

#26008: setup() missing 1 required positional argument: 'parallel' when running
runtest.py --pair or runtests.py --bisect
---+
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * component:  Uncategorized => Testing framework
 * needs_tests:   => 0
 * needs_docs:   => 0


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

Re: [Django] #26003: Add a "how the documentation is organized" explanation

[Django]

#26003: Add a "how the documentation is organized" explanation
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I've updated the pull request as you've requested.

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

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
--+
 Reporter:  chmarr|Owner:  chmarr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by chmarr):

 Thank you for the link to the changes. I'll set up a test case.

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

Re: [Django] #26007: SingleObjectTemplateResponseMixin.get_template_names does not return names stack properly.

[Django]

#26007: SingleObjectTemplateResponseMixin.get_template_names does not return 
names
stack properly.
---+
 Reporter:  chmarr |Owner:  chmarr
 Type:  Bug|   Status:  assigned
Component:  Generic views  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by chmarr):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Pull request: https://github.com/django/django/pull/5892

 All tests pass. Documentation compiles.

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

Re: [Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+--
 Reporter:  knbk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.9
 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 knbk):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> 2 models in tests/order_with_respect_to/models.py are missing an explicit
> app_label.
>
> {{{
> $ python runtests.py --parallel=1
> contenttypes_tests.test_order_with_respect_to
> Testing against Django installed in '/vagrant/django/django'
> Traceback (most recent call last):
>   File "runtests.py", line 450, in 
> options.debug_sql, options.parallel)
>   File "runtests.py", line 267, in django_tests
> extra_tests=extra_tests,
>   File "/vagrant/django/django/test/runner.py", line 531, in run_tests
> suite = self.build_suite(test_labels, extra_tests)
>   File "/vagrant/django/django/test/runner.py", line 422, in build_suite
> tests = self.test_loader.loadTestsFromName(label)
>   File "/usr/lib/python3.4/unittest/loader.py", line 105, in
> loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File
> "/vagrant/django/tests/contenttypes_tests/test_order_with_respect_to.py",
> line 1, in 
> from order_with_respect_to.tests import (
>   File "/vagrant/django/tests/order_with_respect_to/tests.py", line 9, in
> 
> from .models import Answer, Dimension, Entity, Post, Question
>   File "/vagrant/django/tests/order_with_respect_to/models.py", line 48,
> in 
> class Entity(models.Model):
>   File "/vagrant/django/django/db/models/base.py", line 102, in __new__
> "INSTALLED_APPS." % (module, name)
> RuntimeError: Model class order_with_respect_to.models.Entity doesn't
> declare an explicit app_label and isn't in an application in
> INSTALLED_APPS.
> }}}

New description:

 3 models in `tests/order_with_respect_to/models.py` are missing an
 explicit `app_label`.

 {{{
 $ python runtests.py --parallel=1
 contenttypes_tests.test_order_with_respect_to
 Testing against Django installed in '/vagrant/django/django'
 Traceback (most recent call last):
   File "runtests.py", line 450, in 
 options.debug_sql, options.parallel)
   File "runtests.py", line 267, in django_tests
 extra_tests=extra_tests,
   File "/vagrant/django/django/test/runner.py", line 531, in run_tests
 suite = self.build_suite(test_labels, extra_tests)
   File "/vagrant/django/django/test/runner.py", line 422, in build_suite
 tests = self.test_loader.loadTestsFromName(label)
   File "/usr/lib/python3.4/unittest/loader.py", line 105, in
 loadTestsFromName
 module = __import__('.'.join(parts_copy))
   File
 "/vagrant/django/tests/contenttypes_tests/test_order_with_respect_to.py",
 line 1, in 
 from order_with_respect_to.tests import (
   File "/vagrant/django/tests/order_with_respect_to/tests.py", line 9, in
 
 from .models import Answer, Dimension, Entity, Post, Question
   File "/vagrant/django/tests/order_with_respect_to/models.py", line 48,
 in 
 class Entity(models.Model):
   File "/vagrant/django/django/db/models/base.py", line 102, in __new__
 "INSTALLED_APPS." % (module, name)
 RuntimeError: Model class order_with_respect_to.models.Entity doesn't
 declare an explicit app_label and isn't in an application in
 INSTALLED_APPS.
 }}}

--

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

[Django] #26009: contenttypes_tests fail when run in isolation

[Django]

#26009: contenttypes_tests fail when run in isolation
---+
 Reporter:  knbk   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 2 models in tests/order_with_respect_to/models.py are missing an explicit
 app_label.

 {{{
 $ python runtests.py --parallel=1
 contenttypes_tests.test_order_with_respect_to
 Testing against Django installed in '/vagrant/django/django'
 Traceback (most recent call last):
   File "runtests.py", line 450, in 
 options.debug_sql, options.parallel)
   File "runtests.py", line 267, in django_tests
 extra_tests=extra_tests,
   File "/vagrant/django/django/test/runner.py", line 531, in run_tests
 suite = self.build_suite(test_labels, extra_tests)
   File "/vagrant/django/django/test/runner.py", line 422, in build_suite
 tests = self.test_loader.loadTestsFromName(label)
   File "/usr/lib/python3.4/unittest/loader.py", line 105, in
 loadTestsFromName
 module = __import__('.'.join(parts_copy))
   File
 "/vagrant/django/tests/contenttypes_tests/test_order_with_respect_to.py",
 line 1, in 
 from order_with_respect_to.tests import (
   File "/vagrant/django/tests/order_with_respect_to/tests.py", line 9, in
 
 from .models import Answer, Dimension, Entity, Post, Question
   File "/vagrant/django/tests/order_with_respect_to/models.py", line 48,
 in 
 class Entity(models.Model):
   File "/vagrant/django/django/db/models/base.py", line 102, in __new__
 "INSTALLED_APPS." % (module, name)
 RuntimeError: Model class order_with_respect_to.models.Entity doesn't
 declare an explicit app_label and isn't in an application in
 INSTALLED_APPS.
 }}}

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

Re: [Django] #20846: Increase contrib.auth's User.username length

[Django]

#20846: Increase contrib.auth's User.username length
-+
 Reporter:  ivoras@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by collinanderson):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/5891

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

[Django] #26008: setup() missing 1 required positional argument: 'parallel' when running runtest.py --pair or runtests.py --bisect

[Django]

#26008: setup() missing 1 required positional argument: 'parallel' when running
runtest.py --pair or runtests.py --bisect
---+
 Reporter:  knbk   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Full traceback:

 {{{
 Traceback (most recent call last):
   File "runtests.py", line 445, in 
 paired_tests(options.pair, options, options.modules)
   File "runtests.py", line 332, in paired_tests
 state = setup(options.verbosity, test_labels)
 TypeError: setup() missing 1 required positional argument: 'parallel'
 }}}

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

Re: [Django] #20846: Increase contrib.auth's User.username length

[Django]

#20846: Increase contrib.auth's User.username length
-+
 Reporter:  ivoras@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 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
-+

Comment (by collinanderson):

 Actually, I think the shorter index solution doesn't work for UNIQUE
 indexes, which is what we're running into here.
 https://groups.google.com/d/msg/django-developers/DuSwAy0670w/wS2ohfFVDwAJ

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

Re: [Django] #26007: SingleObjectTemplateResponseMixin.get_template_names does not return names stack properly.

[Django]

#26007: SingleObjectTemplateResponseMixin.get_template_names does not return 
names
stack properly.
---+--
 Reporter:  chmarr |Owner:  chmarr
 Type:  Bug|   Status:  assigned
Component:  Generic views  |  Version:  1.9
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by chmarr):

 * owner:  nobody => chmarr
 * status:  new => assigned
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

[Django] #26007: SingleObjectTemplateResponseMixin.get_template_names does not return names stack properly.

[Django]

#26007: SingleObjectTemplateResponseMixin.get_template_names does not return 
names
stack properly.
---+
 Reporter:  chmarr |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Generic views  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The docstring for SingleObjectTemplateResponseMixin.get_template_names()
 implies that a particular list of names is being returned. However, if
 SingleObjectTemplateResponseMixin.get_template_names() (the super) returns
 anything, then only the template_name will be returned.

 In addition, the name obtained by using self.template_name_field is
 inserted at 0, implying that there is something to insert it in front of,
 which is impossible given the current implementation, and conflicts with
 the documentation.

 By inference, it appears that the intended implementation is that the
 following names are returned, in this order:
 * a template derived from the template_name_field field of the object.
 * a template derived from the super (the template_name) attribute of the
 view
 * a template derived from the object's model name or self.model's name,
 with the template_name_suffix appended.

 Change will need some refactoring of the method, change to the docstring,
 and the documentation. I'll provide a pull request.

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

Re: [Django] #25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`

[Django]

#25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`
--+--
 Reporter:  jimgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  JSONB | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by jimgraham):

 I think serializing would be be optional at the model level, and the user
 could decide how they wanted objects serialized/deserialize. The default
 would continue to be no serialization.

 Is it worthwhile coming up with a PR for comments, or is this a non-
 starter?

 Thanks.

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

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
--+
 Reporter:  chmarr|Owner:  chmarr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * version:  1.9 => master
 * needs_tests:  0 => 1


Comment:

 The change makes sense.

 This should be good to go once you add a regression test or adjust
 
[https://github.com/chmarr/django/commit/86aaffa5a3510c007167d116cf4ad72b79e93f31
 the ones added by this check].

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

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
--+
 Reporter:  chmarr|Owner:  chmarr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Generic views |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by chmarr):

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

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
-+-
 Reporter:  chmarr   |Owner:  chmarr
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Generic views|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chmarr):

 * owner:  nobody => chmarr
 * status:  new => assigned
 * has_patch:  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/064.7a39b7d3afd2094412fbf98d090eb2a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
-+-
 Reporter:  chmarr   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Generic views|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chmarr):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Pull request: https://github.com/django/django/pull/5890

 All tests pass under SQLite.

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

[Django] #26006: SingleObjectMixin.get_context_object_name refers to obj and self.object inconsistently

[Django]

#26006: SingleObjectMixin.get_context_object_name refers to obj and self.object
inconsistently
--+
 Reporter:  chmarr|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Generic views |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The method SingleObjectMixin.get_context_object_name refers to the 'obj'
 parameter several times, but in one instance refers to self.object in a
 seemingly inconsistent manner.

 This is probably not causing a problem, yet, since the descendant class,
 typically BaseDetailView, is setting self.object, and
 SingleObjectMixin.get_context_data simply calls
 self.get_context_object_name(self.object), so the two are _usually_ the
 same object.

 Trivial bug, and trivial fix. I'll create a pull request. Test suite
 passes both before and after the change.

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

Re: [Django] #26003: Add a "how the documentation is organized" explanation

[Django]

#26003: Add a "how the documentation is organized" explanation
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by EvilDMP):

 Maybe it should also include (or perhaps it should be noted elsewhere, in
 the "how to contribute to the documentation" section) some notes on how
 the documentation in these sections should be be written.

 e.g.

 * tutorials: don't try to explain how things work ''before'' a step; any
 explanations should come afterwards and refer to what has been done (on
 the other hand it ''is'' appropriate to explain the nature of the problem
 we're solving so that the reader understands what we're trying to achieve)
 * how-to: what matters most is what a user wants to achieve, so a how-to
 should always be result-oriented rather than focused on details of
 Django's implementation of whatever it is we're discussing
 * reference: try to keep reference material as tightly focused on the
 subject as possible; generally you should assume that the reader already
 understands the basic concepts involved, but needs to know or be reminded
 how Django does it; if you find yourself explaining concepts, you may want
 to move that material to the ''topic'' section
 * topic: link to reference material rather than repeating it; use
 examples; don't be reluctant to explain even things that you consider very
 basic

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

Re: [Django] #22822: Javascript en_* translations ignored if no en or en_us translations exist

[Django]

#22822: Javascript en_* translations ignored if no en or en_us translations 
exist
-+-
 Reporter:  pforth@… |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Tests aren't passing.

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

Re: [Django] #25316: Can't use order_by and values(_list) together after annotating

[Django]

#25316: Can't use order_by and values(_list) together after annotating
-+-
 Reporter:  adrian17 |Owner:
 |  varunnaganathan
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  annotate, order_by   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is erroneous

[Django]

#25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is
erroneous
-+
 Reporter:  kuna |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:  slash,debug  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by tripples):

 I was facing same issue after upgrading to Django 1.9. When DEBUG=False
 redirection was not happening. Applied above patch manually on production
 system. Helped for me.


 Case 1(Issue):
 When DEBUG=False,
 example.com/sample
 Returns 404.

 Case 2:
 Whereas with DEBUG=True
 example.com/sample/
 Return 301

 Thanks,
 Sanket

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

Re: [Django] #22822: Javascript en_* translations ignored if no en or en_us translations exist

[Django]

#22822: Javascript en_* translations ignored if no en or en_us translations 
exist
-+-
 Reporter:  pforth@… |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_tests:  1 => 0


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

[Django] #26005: uri_to_iri() broken

[Django]

#26005: uri_to_iri() broken
---+
 Reporter:  Chronial   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Core (URLs)|Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The current implementation of uri_to_iri is incorrect.

 In step two of [http://tools.ietf.org/html/rfc3987.html#section-3.2 the
 algorithm], it should:

 > Convert all percent-encodings ("%" followed by two hexadecimal
 digits) to the corresponding octets, except those corresponding   to
 "%", characters in "reserved", and characters in US-ASCII not
 allowed in URIs.

 But instead it just runs an unquote
 
([https://github.com/django/django/blob/dbb0df2a0ec5bee80bee336fc81408efb30b7e47/django/utils/encoding.py#L199
 source])

 This also makes this statement from
 [https://docs.djangoproject.com/en/1.9/ref/unicode/#uri-and-iri-handling
 the docs] a lie:

 > Both iri_to_uri() and uri_to_iri() functions are idempotent, which means
 the following is always true:
 > uri_to_iri(uri_to_iri(some_string)) == uri_to_iri(some_string)

 But at the moment

 {{{
 uri_to_iri(uri_to_iri("%2525")) == "%" != "%25" == uri_to_iri("%2525")
 }}}

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

Re: [Django] #25985: Update signature of ModelAdmin.formfield_for_* to make request a positional argument

[Django]

#25985: Update signature of ModelAdmin.formfield_for_* to make request a 
positional
argument
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"dbb0df2a0ec5bee80bee336fc81408efb30b7e47" dbb0df2]:
 {{{
 #!CommitTicketReference repository=""
 revision="dbb0df2a0ec5bee80bee336fc81408efb30b7e47"
 Fixed #25985 -- Updated signature of ModelAdmin.formfield_for_* to make
 request a positional argument.
 }}}

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

[Django] #26004: Invalid app-name in INSTALLED_APPS leads to AppRegistryNotReady when testing

[Django]

#26004: Invalid app-name in INSTALLED_APPS leads to AppRegistryNotReady when
testing
---+
 Reporter:  HM |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When testing a standalone app, with a runtests.py like so:

 {{{
 import sys
 import os

 os.environ['DJANGO_SETTINGS_MODULE'] = 'app.tests.settings'

 from django.conf import settings
 from django.test.utils import get_runner

 if __name__ == '__main__':
 from django import setup
 setup()

 TestRunner = get_runner(settings)

 test_runner = TestRunner()
 failures = test_runner.run_tests(settings.INSTALLED_APPS)

 if failures:
 sys.exit(bool(failures))
 }}}

 ... and there is a typo in INSTALLED_APPS, instead of an ImportError
 pointing towards the wrong app-name there's an AppRegistryNotReady.

 This holds for both 1.8.7 and 1.9.

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

Re: [Django] #19536: in ModelAdmin disabling has_add_permission results in not showing any object-tools

[Django]

#19536: in ModelAdmin disabling has_add_permission results in not showing any
object-tools
--+
 Reporter:  a.fazeli@…|Owner:  ikks
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ff19df9c2d6ad80bb9177e8190176e9c3716705f" ff19df9]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff19df9c2d6ad80bb9177e8190176e9c3716705f"
 Fixed #19536 -- Included object-tools when ModelAdmin.has_add_permission()
 is False.
 }}}

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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  sasha0
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.9
 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 sasha0):

 * owner:  nobody => sasha0
 * 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.1866a01017cf98c7fed91172efa8af2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by teeberg):

 * cc: teeberg (added)


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

Re: [Django] #26003: Add a "how the documentation is organized" explanation

[Django]

#26003: Add a "how the documentation is organized" explanation
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5888 PR]

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

[Django] #26003: Add a "how the documentation is organized" explanation

[Django]

#26003: Add a "how the documentation is organized" explanation
-+-
   Reporter:  timgraham  |  Owner:  timgraham
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  1.9
  Documentation  |
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 As discussion [https://groups.google.com/d/topic/django-
 developers/QW06ctKbFKA/discussion on django-developers], the documentation
 structure of intro, topic, ref, howto isn't obvious to many people.

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

Re: [Django] #25104: Documentation assumes that there's a httpd.conf

[Django]

#25104: Documentation assumes that there's a httpd.conf
--+
 Reporter:  ChristianKleineidam   |Owner:  za
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"0d6633df93c41f3999db0fd1551a6bc627f4bf57" 0d6633d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d6633df93c41f3999db0fd1551a6bc627f4bf57"
 [1.9.x] Fixed #25104 -- Added httpd.conf hyperlink to modwsgi doc.

 Backport of d9e150b3117521f7c24dc6393eb29eebc3cc376a from master
 }}}

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

Re: [Django] #25104: Documentation assumes that there's a httpd.conf

[Django]

#25104: Documentation assumes that there's a httpd.conf
--+
 Reporter:  ChristianKleineidam   |Owner:  za
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d9e150b3117521f7c24dc6393eb29eebc3cc376a" d9e150b]:
 {{{
 #!CommitTicketReference repository=""
 revision="d9e150b3117521f7c24dc6393eb29eebc3cc376a"
 Fixed #25104 -- Added httpd.conf hyperlink to modwsgi doc.
 }}}

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

Re: [Django] #20869: Prevent repetitive output to counter BREACH-type attacks

[Django]

#20869: Prevent repetitive output to counter BREACH-type attacks
-+
 Reporter:  patrys   |Owner:  shaib
 Type:  New feature  |   Status:  assigned
Component:  CSRF |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement and there's also a failing test.

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

Re: [Django] #23372: Test suite initial database construction is too slow

[Django]

#23372: Test suite initial database construction is too slow
--+
 Reporter:  manfre|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Anssi has proposed [https://github.com/django/django/pull/5801 an
 alternate approach].

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

[Django] #26002: Improve ModelAdmin.get_search_results() example

[Django]

#26002: Improve ModelAdmin.get_search_results() example
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.9
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 There are two main issues:
 * Clarify why the current example is the way it is instead of simply
 listing 'age' in `search_fields`.
 * Add other use cases like plugging in Solr or Haystack results, or
 defining some custom search operators (+, -, *, @, ...)

 [https://github.com/django/django/pull/5883 discussion on a pull request].

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

[Django] #26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields

[Django]

#26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.admin |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Currently,
 [https://github.com/django/django/pull/5883#issuecomment-167767767 all
 queries are done as string lookups] which gives something like this on
 PostgreSQL, for example:
 `("admin_views_pluggablesearchperson"."age"::text) = UPPER(20))`. It would
 be more efficient if the admin cast the search value to an integer and
 used that for the query.

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

Re: [Django] #26000: Error in tutorial05 Django1.9

[Django]

#26000: Error in tutorial05 Django1.9
-+-
 Reporter:  philbert |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  AttributeError   | Triage Stage:
  DetailView pk slug |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => worksforme
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I think you probably make a mistake along the way, but you'll need to
 provide your project so that we can help identify the issue. Please see
 TicketClosingReasons/UseSupportChannels for ways to get help.

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

[Django] #26000: Error in tutorial05 Django1.9

[Django]

#26000: Error in tutorial05 Django1.9
---+---
 Reporter:  philbert   |  Owner:  nobody
 Type:  Bug| Status:  new
Component: |Version:  1.9
  Documentation|
 Severity:  Normal |   Keywords:  AttributeError DetailView pk slug
 Triage Stage: |  Has patch:  0
  Unreviewed   |
Easy pickings:  0  |  UI/UX:  0
---+---
 After following the directions here:
 https://docs.djangoproject.com/en/1.9/intro/tutorial05/

 These two tests return the same error:

 ERROR: test_detail_view_with_a_future_question
 (polls.tests.QuestionIndexDetailTests)

 ERROR: test_detail_view_with_a_past_question
 (polls.tests.QuestionIndexDetailTests)

 AttributeError: Generic detail view DetailView must be called with either
 an object pk or a slug.

 Discovered this suggestion but didn't manage to get it to work.
 Not sure what the correct solution should be.
 http://chriskief.com/2012/12/29/django-generic-detailview-without-a-pk-or-
 slug/

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

[Django] #25999: Document why Django makes its deprecation warnings loud by default and how to silence them

[Django]

#25999: Document why Django makes its deprecation warnings loud by default and 
how
to silence them
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 See #18985 for the background of why we route warnings through logging.

 A developer can selectively silence warnings using something like this in
 an app's `AppConfig.ready()` method:
 {{{
 import warnings
 from django.utils.deprecation import RemovedInNextVersionWarning
 warnings.simplefilter("ignore", RemovedInNextVersionWarning)
 }}}
 This example can be improved to show how to silence a particular warning
 instead of all warnings.

 This works because `AppConfig.ready()` methods are called after
 `django.utils.log.configure_logging()` (which does
 `warnings.simplefilter("default", RemovedInNextVersionWarning)`) in
 `django.setup()`.

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

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

[Django]

#25465: Line breaks in readonly field in admin tabular inline
+
 Reporter:  pcraston|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  tabular inline  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


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

Re: [Django] #25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`

[Django]

#25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`
--+--
 Reporter:  jimgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  JSONB | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by timgraham):

 * cc: mjtamlyn (added)
 * needs_better_patch:   => 0
 * component:  Database layer (models, ORM) => contrib.postgres
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I think the problem here is that we couldn't also deserialize that data
 since we have no way to know if the user originally passed a string or
 some other Python type. For example, if we see '1' in the JSONField, do we
 deserialize it to 1 (integer) or leave it as a string? Using
 `DjangoJSONEncoder` for model serialization is different because we have
 the model field type hint to use for deserialization.

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

Re: [Django] #25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid field

[Django]

#25997: Editing ForeignKey in admin popup causes incorrect escaping for uuid 
field
-+
 Reporter:  zachborboa   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.9
 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 timgraham):

 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.admin
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Regression in 1.9 bisected to 845817b039fc059955bb1eafa5fd78565a49159d.

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

Re: [Django] #25998: SQLCompiler error when using Paginator + values(...) when query returns no data

[Django]

#25998: SQLCompiler error when using Paginator + values(...) when query returns 
no
data
-+-
 Reporter:  awbacker |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  SQLCompiler, | Triage Stage:
  Paginator, values  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by awbacker):

 Installed `Django==1.9.1.dev20151228224945` directly from github and the
 issue is fixed.

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

Re: [Django] #25165: Move JavaScript calls out of HTML to fix JavaScript "no-script-eval" warnings

[Django]

#25165: Move JavaScript calls out of HTML to fix JavaScript "no-script-eval"
warnings
-+-
 Reporter:  timgraham|Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  new
Component:  contrib.admin|  Version:  master
 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
-+-

Comment (by timgraham):

 Another regression: when using the "Add another" button on a foreign key
 to a `UUIDField` in the admin, the
 
[https://github.com/django/django/blob/35c41987ecfaad849019d09468ce322fec86cd39/django/contrib/admin/options.py#L1086-L1090
 JSON serialization] will fail with `TypeError: UUID('f9cd8eb4-7c00-407b-
 bc35-17a8a8d0b9f0') is not JSON serializable`.

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

Re: [Django] #25998: SQLCompiler error when using Paginator + values(...) when query returns no data

[Django]

#25998: SQLCompiler error when using Paginator + values(...) when query returns 
no
data
-+-
 Reporter:  awbacker |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  SQLCompiler, | Triage Stage:
  Paginator, values  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by awbacker:

Old description:

> I am experiencing a crash in the `SQLCompiler` when I try to execute a
> paginated query after calling `.values(...)`.
>
> {{{
> AttributeError: 'SQLCompiler' object has no attribute 'col_count'
> }}}
>
> * Postgres 9.3, psycopg2==2.6.1
> * Django 1.9
> * No data is present in the table
>
> {{{
> # Query must have NO data returned for it
> qs = Room.objects.values('id')
> pg = Paginator(per_page=1, object_list=qs)
> res = list(pg.page(0))
>
> class Room(models.Model):
> has_tv = models.BooleanField()
> }}}
>
> {{{
> ==
> ERROR: test_pure_django (api.tests.test_api_call.TestApiCall)
> --
> Traceback (most recent call last):
>   File "/Users/andrew/dev/st/abc/api/tests/test_api_call.py", line 25, in
> test_pure_django
> res = list(pg.page(1))
>   File "/Users/andrew/dev/st/abc/venv/bin/../lib/python2.7/_abcoll.py",
> line 602, in __iter__
> v = self[i]
>   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
> packages/django/core/paginator.py", line 125, in __getitem__
> self.object_list = list(self.object_list)
>   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
> packages/django/db/models/query.py", line 258, in __iter__
> self._fetch_all()
>   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
> packages/django/db/models/query.py", line 1074, in _fetch_all
> self._result_cache = list(self.iterator())
>   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
> packages/django/db/models/query.py", line 112, in __iter__
> for row in compiler.results_iter():
>   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
> packages/django/db/models/sql/compiler.py", line 807, in results_iter
> fields = [s[0] for s in self.select[0:self.col_count]]
> AttributeError: 'SQLCompiler' object has no attribute 'col_count'
> }}}
>
> I have a fairly minimal reproduction, and can try to reduce it even
> further (removing DRF, psycopg2, etc) if needed.  I don't think it's an
> issue with postgres.  I think it has something to do with the
> ValuesIterable, but have no way of telling for sure.

New description:

 I am experiencing a crash in the `SQLCompiler` when I try to execute a
 paginated query after calling `.values(...)`.

 {{{
 AttributeError: 'SQLCompiler' object has no attribute 'col_count'
 }}}

 * Postgres 9.3, psycopg2==2.6.1
 * Django 1.9
 * No data is present in the table

 {{{
 # Query must have NO data returned for it
 qs = Room.objects.values('id')
 pg = Paginator(per_page=1, object_list=qs)
 res = list(pg.page(1))

 class Room(models.Model):
 has_tv = models.BooleanField()
 }}}

 {{{
 ==
 ERROR: test_pure_django (api.tests.test_api_call.TestApiCall)
 --
 Traceback (most recent call last):
   File "/Users/andrew/dev/st/abc/api/tests/test_api_call.py", line 25, in
 test_pure_django
 res = list(pg.page(1))
   File "/Users/andrew/dev/st/abc/venv/bin/../lib/python2.7/_abcoll.py",
 line 602, in __iter__
 v = self[i]
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/core/paginator.py", line 125, in __getitem__
 self.object_list = list(self.object_list)
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 258, in __iter__
 self._fetch_all()
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 1074, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 112, in __iter__
 for row in compiler.results_iter():
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 807, in results_iter
 fields = [s[0] for s in self.select[0:self.col_count]]
 AttributeError: 

Re: [Django] #25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is erroneous

[Django]

#25878: APPEND_SLASH doesn't work with DEBUG=False when template/404.html is
erroneous
-+
 Reporter:  kuna |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.9
 Severity:  Release blocker  |   Resolution:
 Keywords:  slash,debug  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

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

Re: [Django] #25989: sitemap view picks lastmod from last supplied sitemap only

[Django]

#25989: sitemap view picks lastmod from last supplied sitemap only
--+
 Reporter:  allixx|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sitemaps  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  sitemap lastmod   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by allixx):

 * needs_tests:  1 => 0


Comment:

 Tests added to pull request.

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

Re: [Django] #25996: Revise the Performance section in topics/http/urls (was: Remove the Performance section in topics/http/urls)

[Django]

#25996: Revise the Performance section in topics/http/urls
--+
 Reporter:  uranusjr  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   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 timgraham):

 * cc: knbk (added)
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 I'd suggest to revise the section to describe what parts of the URL system
 are fast (routing URLs, I think) and what parts are slow (reversing URLs,
 I think). There are probably other considerations. Marten might be in a
 good position to do this since he's been working on some
 [https://github.com/django/django/pull/5578 URL dispatcher changes].

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

Re: [Django] #25998: SQLCompiler error when using Paginator + values(...) when query returns no data

[Django]

#25998: SQLCompiler error when using Paginator + values(...) when query returns 
no
data
-+-
 Reporter:  awbacker |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  SQLCompiler, | Triage Stage:
  Paginator, values  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug


Comment:

 This looks like a duplicate of #25894 which will be fixed in the upcoming
 1.9.1 release. Can you verify the issue is fixed for you on the
 `stable/1.9.x` branch and reopen if not? Thanks.

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

[Django] #25998: SQLCompiler error when using Paginator + values(...) when query returns no data

[Django]

#25998: SQLCompiler error when using Paginator + values(...) when query returns 
no
data
-+-
 Reporter:  awbacker |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.9
  (models, ORM)  |   Keywords:  SQLCompiler, Paginator,
 Severity:  Normal   |  values
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I am experiencing a crash in the `SQLCompiler` when I try to execute a
 paginated query after calling `.values(...)`.

 {{{
 AttributeError: 'SQLCompiler' object has no attribute 'col_count'
 }}}

 * Postgres 9.3, psycopg2==2.6.1
 * Django 1.9
 * No data is present in the table

 {{{
 # Query must have NO data returned for it
 qs = Room.objects.values('id')
 pg = Paginator(per_page=1, object_list=qs)
 res = list(pg.page(0))

 class Room(models.Model):
 has_tv = models.BooleanField()
 }}}

 {{{
 ==
 ERROR: test_pure_django (api.tests.test_api_call.TestApiCall)
 --
 Traceback (most recent call last):
   File "/Users/andrew/dev/st/abc/api/tests/test_api_call.py", line 25, in
 test_pure_django
 res = list(pg.page(1))
   File "/Users/andrew/dev/st/abc/venv/bin/../lib/python2.7/_abcoll.py",
 line 602, in __iter__
 v = self[i]
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/core/paginator.py", line 125, in __getitem__
 self.object_list = list(self.object_list)
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 258, in __iter__
 self._fetch_all()
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 1074, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 112, in __iter__
 for row in compiler.results_iter():
   File "/Users/andrew/dev/st/abc/venv/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 807, in results_iter
 fields = [s[0] for s in self.select[0:self.col_count]]
 AttributeError: 'SQLCompiler' object has no attribute 'col_count'
 }}}

 I have a fairly minimal reproduction, and can try to reduce it even
 further (removing DRF, psycopg2, etc) if needed.  I don't think it's an
 issue with postgres.  I think it has something to do with the
 ValuesIterable, but have no way of telling for sure.

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

Re: [Django] #25987: Creating new object in admin with child model inlines and unique_together raises IntegrityError

[Django]

#25987: Creating new object in admin with child model inlines and 
unique_together
raises IntegrityError
-+-
 Reporter:  MrYoda   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  admin, create| Triage Stage:  Accepted
  object, unique_together,   |
  IntegrityError, validate_unique|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MrYoda):

 In my humble opinion of django's middle developer, the issue can be
 reproduced in all cases when we use BaseModelFormSet or its descendants.
 In most cases it's used in admin (and without overriding of buggy method).

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