Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  MarkusH
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | 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 MarkusH):

 Oh, missed that. Thanks Carl.

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

Re: [Django] #24899: Split up migrations autodetector._detect_changes into separate functions

[Django]

#24899: Split up migrations autodetector._detect_changes into separate functions
-+-
 Reporter:  MarkusH  |Owner:
 Type:   |  iamsteadman
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  afraid-to-commit | Triage Stage:  Ready for
 |  checkin
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:"ed63df3fc2f0c228354ca3435e9bed45be9d0909" ed63df3]:
 {{{
 #!CommitTicketReference repository=""
 revision="ed63df3fc2f0c228354ca3435e9bed45be9d0909"
 Fixed #24899 -- Split migrations autodetector._detect_changes() 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/065.5966f8bf3de192edb9247cebd05620dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22316: TimeField lacks hour/minute filters

[Django]

#22316: TimeField lacks hour/minute filters
-+-
 Reporter:  dracos   |Owner:  dracos
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2dc93bb10ab1c2af1df9977f1b51d47cadab7b21" 2dc93bb]:
 {{{
 #!CommitTicketReference repository=""
 revision="2dc93bb10ab1c2af1df9977f1b51d47cadab7b21"
 Fixed #22316 -- Added time filters to TimeField on SQLite.

 This was implemented for non-SQLite backends in 1.7 (as a
 side effect of #16187).
 }}}

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

Re: [Django] #19210: django.utils.timesince() does not account for leap years

[Django]

#19210: django.utils.timesince() does not account for leap years
---+
 Reporter:  jnns   |Owner:  raphaelm
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  date time  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6700c909358d2ff9ff96f28dbc549906d8d32206" 6700c90]:
 {{{
 #!CommitTicketReference repository=""
 revision="6700c909358d2ff9ff96f28dbc549906d8d32206"
 Fixed #19210 -- Added leap year support to django.utils.timesince()
 }}}

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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


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

Re: [Django] #24911: QuerySet is initiated with model=None as kwarg, but is called in BaseManager.get_queryset() as arg.

[Django]

#24911: QuerySet is initiated with model=None as kwarg, but is called in
BaseManager.get_queryset() as arg.
-+-
 Reporter:  317070   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_tests:  0 => 1
 * 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.4dc786378417da1c26dd1201ca406306%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24928: Add UUIDField, RangeField, etc to database introspection

[Django]

#24928: Add UUIDField, RangeField, etc to database introspection
-+-
 Reporter:  MarkusH  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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):

 * type:  Bug => New feature
 * stage:  Unreviewed => Accepted


Comment:

 There's an interesting question about how contrib.postgres can
 "contribute" introspection rules to the postgres backend. Maybe the
 contrib.postgres fields should be handled in a separate ticket.

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

Re: [Django] #24829: TemplateView raises unhandled ContentNotRenderedError error when used as error handler

[Django]

#24829: TemplateView raises unhandled ContentNotRenderedError error when used as
error handler
---+--
 Reporter:  nonZero|Owner:  ana-balica
 Type:  New feature|   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:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/4777 PR] which needs 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/065.115a2775db1c777f84432ee34c01bbc0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
-+-
 Reporter:  gannetson|Owner:  gannetson
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0207bdd2d4157c542c981264c86706b78ca246e9" 0207bdd]:
 {{{
 #!CommitTicketReference repository=""
 revision="0207bdd2d4157c542c981264c86706b78ca246e9"
 Fixed #24474 -- Allowed configuring the admin's empty change list value.
 }}}

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

Re: [Django] #24159: compilemessages does not behave the same as makemessages

[Django]

#24159: compilemessages does not behave the same as makemessages
-+-
 Reporter:  dracos   |Owner:  dracos
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"40f0a84cb151669313faadf857aaddd18d39aaeb" 40f0a84c]:
 {{{
 #!CommitTicketReference repository=""
 revision="40f0a84cb151669313faadf857aaddd18d39aaeb"
 Fixed #24159 -- Made compilemessages run across all apps.

 Updated the command to match the documentation, which states it
 runs over all .po files.
 }}}

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

Re: [Django] #24904: reverse() doesn't allow for nested current_app namespaces

[Django]

#24904: reverse() doesn't allow for nested current_app namespaces
-+-
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | 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):

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  MarkusH
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | 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):

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
--+
 Reporter:  knbk  |Owner:  MarkusH
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Utilities |  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
--+

Comment (by carljm):

 @markush there was already a PR contributed, see above

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
--+
 Reporter:  knbk  |Owner:  MarkusH
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Utilities |  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 MarkusH):

 * stage:  Unreviewed => Accepted


Comment:

 PR: https://github.com/django/django/pull/4788

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

Re: [Django] #24907: Update the contributing tutorial to use a more recent patch

[Django]

#24907: Update the contributing tutorial to use a more recent patch
-+-
 Reporter:  giuliettamasina  |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 giuliettamasina):

 * has_patch:  0 => 1


Comment:

 Opened pull request: https://github.com/django/django/pull/4787

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.d727a47d05cd4a8e4e86a09e747af556%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  MarkusH
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 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 MarkusH):

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

[Django] #24928: Add UUIDField, RangeField, etc to database introspection

[Django]

#24928: Add UUIDField, RangeField, etc to database introspection
-+-
   Reporter:  MarkusH|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 
django.db.backends.postgresql_psycopg2.introspection.DatabaseIntrospection.data_types_reverse
 does not handle UUIDField and other core or contrib.postgres specific
 fields. And neither does any of the other backends.

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 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
-+-

Comment (by carljm):

 I don't think it's worth putting users through a deprecation process on
 the import location of `python_2_unicode_compatible`, when we could just
 provide a non-deprecated import shim and leave it there until Python 2
 support is dropped entirely. That's a lot of hassle for Django users in
 order to save us a single import line in `django.utils.encoding`.

 I do think it's good to switch to relying on the implementation in `six`.

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 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 coldmind):

 * cc: me@… (added)
 * easy:  1 => 0


Comment:

 If we're going to use the method from `six`, seems we should to deprecate
 import from django utils, and replace imports inside the django code to
 use `six` import instead of utils.

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

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 jarshwah):

 Yes, a loop will do. We'll also need to fail if an aggregate is provided
 multiple source_expressions but no alias. See
 
https://github.com/django/django/blob/3e9b5bfd9c3e16c968278f7d050f52739690eb29/django/db/models/aggregates.py#L22
 and
 
https://github.com/django/django/blob/3e9b5bfd9c3e16c968278f7d050f52739690eb29/django/db/models/aggregates.py#L34

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

Re: [Django] #24925: Coalesce converts datetime to string on MySQL

[Django]

#24925: Coalesce converts datetime to string on MySQL
-+-
 Reporter:  Ian-Foote|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
-+-

Comment (by jarshwah):

 Is this an issue with MySQL or the implementation of Coalesce within
 Django? That is, does MySQL convert datetimes to strings in coalesce or
 does Django?

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

Re: [Django] #19210: django.utils.timesince() does not account for leap years

[Django]

#19210: django.utils.timesince() does not account for leap years
---+
 Reporter:  jnns   |Owner:  raphaelm
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  date time  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by raphaelm):

 * needs_better_patch:  1 => 0


Comment:

 After looking into a lot of algorithms for date diffing, including the
 ones suggested above and the ones from `python-dateutil` (which get pretty
 complex) I decided to go for the most simple solution I could find. I
 assume `timesince` wasn't ever meant to be an calculation. If we would
 want an exact calculation, we should completely re-implement it to
 correctly work with the different number of days in the months and so on.

 However, there is a very simple fix to the accumulated error that grows
 with the given time period: just use `calendar.leapdays` from the standard
 library and substract it from the number of days.

 I created a pull request including a regression test:
 https://github.com/django/django/pull/4785

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

Re: [Django] #22728: get_or_create with field lookups cause empty values

[Django]

#22728: get_or_create with field lookups cause empty values
-+-
 Reporter:  Xudonax  |Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  get_or_create| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

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


Comment:

 The documentation of `get_or_create` does devote a full paragraph and
 sample code to this, so I don't think there's much to improve.

 There is a case for an extension of the functionality which allows type-
 idempotent transforms such as unaccent or iexact, but I feel this will be
 super hard and prone to bugs. It's a possibility, but not worth keeping
 this lying around for.

 For longer discussion of why this ticket is being closed, see
 https://github.com/django/django/pull/4779

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

Re: [Django] #19210: django.utils.timesince() does not account for leap years

[Django]

#19210: django.utils.timesince() does not account for leap years
---+
 Reporter:  jnns   |Owner:  raphaelm
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  date time  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by raphaelm):

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

Re: [Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-+-
 Reporter:  knbk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by dracos):

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


Comment:

 The function was added to six in 1.9.0, copied from Django's code. PR at
 https://github.com/django/django/pull/4784 to have it include one from the
 other, I was unsure whether it was better to maintain the function in
 encoding.

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

Re: [Django] #22728: get_or_create with field lookups cause empty values

[Django]

#22728: get_or_create with field lookups cause empty values
-+-
 Reporter:  Xudonax  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  get_or_create| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 FWIW, I have code in a current project, written only a few months ago,
 that uses join lookups with `get_or_create`, and takes advantage of the
 fact that they are used in the lookup but not the create. I don't think
 it's an exotic use case, it's simply "find me a user that matches these
 criteria, where the criteria are actually based on related objects, and if
 no such user exists, create a user with the given defaults." That's
 exactly the use case that `get_or_create` is intended for, with the
 addition of "the criteria are based on related objects."

 Even requiring any field mentioned in a lookup to be present in defaults
 is potentially a backwards-incompatible breakage to such use cases. I
 don't know how that change would even handle my case, as the relation I'm
 querying on is not even a field present on User, it's a reverse FK from
 another model, so there's no sensible corresponding value that could be
 included in defaults.

 I see the possible confusion here, but I don't see any way to address it
 without reducing the utility of `get_or_create` in a backwards-
 incompatible way. So I think we should make sure the documentation of
 `get_or_create` is crystal clear on this point, and otherwise leave the
 behavior alone.

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

Re: [Django] #24919: Add an option not to run migrations when running tests

[Django]

#24919: Add an option not to run migrations when running tests
-+
 Reporter:  kairichard   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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
-+

Comment (by shaib):

 #24481 is very closely related (essentially, the same mechanism should be
 used to generate SQL statements. For #24481, they should be printed; here,
 executed).

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

Re: [Django] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
-+
 Reporter:  rooney   |Owner:  Gagaro
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by Gagaro):

 New pull request: https://github.com/django/django/pull/4783

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

Re: [Django] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
-+
 Reporter:  rooney   |Owner:  Gagaro
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Gagaro):

 * owner:  mindsocket => Gagaro
 * needs_docs:  0 => 1
 * 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/064.6d0f9531fcae4e8b00e5cdf9216b8163%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by jcugat):

 When building python with pyenv, it uses the system version of sqlite3
 (3.8.5 in Yosemite), and the segmentation fault occurs.

 To avoid this, install the latest version of sqlite from homebrew
 (3.8.10.2 at the time of this writing):

 {{{
 $ brew install sqlite
 ==> Downloading
 https://homebrew.bintray.com/bottles/sqlite-3.8.10.2.yosemite.bottle.tar.gz
 
 100.0%
 ==> Pouring sqlite-3.8.10.2.yosemite.bottle.tar.gz
 ==> Caveats
 This formula is keg-only, which means it was not symlinked into
 /usr/local.

 Mac OS X already provides this software and installing another version in
 parallel can cause all kinds of trouble.

 OS X provides an older sqlite3.

 Generally there are no consequences of this for you. If you build your
 own software and it requires this formula, you'll need to add to your
 build variables:

 LDFLAGS:  -L/usr/local/opt/sqlite/lib
 CPPFLAGS: -I/usr/local/opt/sqlite/include

 ==> Summary
 🍺  /usr/local/Cellar/sqlite/3.8.10.2: 9 files, 2.8M
 }}}

 And before installing a new python version with pyenv, execute this (the
 paths are taken from the output above):

 {{{
 $ export LDFLAGS="-L/usr/local/opt/sqlite/lib"
 $ export CPPFLAGS="-I/usr/local/opt/sqlite/include"
 $ pyenv install 2.7.10
 }}}

 The compiled python interpreter will use the newer sqlite version from
 homebrew, and no more segfaults!

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

[Django] #24927: django.utils.six and django.utils.encoding both define python_2_unicode_compatible

[Django]

#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
--+
 Reporter:  knbk  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Utilities |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 `django.utils.six` and `django.utils.encoding` define the exact same
 method definition of `python_2_unicode_compatible`, which is not very DRY.
 It might be a good idea to replace one of them with a convenience import
 of the other.

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

Re: [Django] #24912: prefetch_related fails with sqlite3 database and UUIDField primary keys

[Django]

#24912: prefetch_related fails with sqlite3 database and UUIDField primary keys
-+-
 Reporter:  brki |Owner:  brki
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Don't mark your own patch as RFC. Simply uncheck ''Patch needs
 improvement'' once you've addressed the comments on the 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/062.2d8a715949c4fb420a73455dbe35712b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24837: Unable to query DateField using DateRange

[Django]

#24837: Unable to query DateField using DateRange
-+-
 Reporter:  schinckel|Owner:  Marc
 |  Tamlyn 
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Marc Tamlyn ):

 * owner:   => Marc Tamlyn 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"7bda2d8ebc7833747363ac837fecb6535c817dcd" 7bda2d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="7bda2d8ebc7833747363ac837fecb6535c817dcd"
 Fixed #24837 -- field__contained_by=Range

 Provide `contained_by` lookups for the equivalent single valued fields
 related to the range field types. This acts as the opposite direction to
 rangefield__contains.

 With thanks to schinckel for the idea and initial 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/067.909b024706034deaa1f7694f26b9aa43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22316: TimeField lacks hour/minute filters

[Django]

#22316: TimeField lacks hour/minute filters
-+-
 Reporter:  dracos   |Owner:  dracos
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | 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 mjtamlyn):

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

Re: [Django] #24910: createsuperuser in interactive mode assumes USERNAME_FIELD is unique

[Django]

#24910: createsuperuser in interactive mode assumes USERNAME_FIELD is unique
--+--
 Reporter:  carljm|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 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
--+--

Comment (by carljm):

 Yes, there is currently some documentation stating that `USERNAME_FIELD`
 must be a unique field.

 However, the auth checks have clearly been written with the intent to
 allow a non-unique `USERNAME_FIELD`, as long as you are using a custom
 authentication backend. That's why there is both `auth.E003` and
 `auth.W004`. The former is an error, raised if you have a non-unique
 `USERNAME_FIELD` and you are using the default authentication backend
 (which requires `USERNAME_FIELD` to be unique). The latter is merely a
 warning, raised if you have a non-unique `USERNAME_FIELD` and are using a
 custom authentication backend; the warning just reminds you that you need
 to ensure your custom backend can handle non-unique `USERNAME_FIELD` in
 some appropriate way.

 I don't think there is any reason not to allow the latter usage, for
 advanced and unusual cases. So I think that a) `createsuperuser` should be
 updated to only enforce uniqueness if the field is actually unique, and b)
 the `USERNAME_FIELD` doc you linked should be updated to clarify that a
 non-unique `USERNAME_FIELD` is permissible as long as you are using a
 custom auth backend that can handle it.

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

Re: [Django] #24926: text improvement request for deployment guide

[Django]

#24926: text improvement request for deployment guide
--+
 Reporter:  JorisBenschop |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:  1 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 Yes, FastCGI was deprecated and now removed in master so the text you
 propose is okay though we can probably just chop "There’s a number of good
 ways to easily deploy Django:" without replacement. While we're there, it
 might be best to remove the outdated reference to Django Book or update
 the note to mention that it's discussion of FastCGI is also outdated.

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"2aa65460d54b8f8cbca2ae7b7d97bfe219e88929" 2aa6546]:
 {{{
 #!CommitTicketReference repository=""
 revision="2aa65460d54b8f8cbca2ae7b7d97bfe219e88929"
 [1.8.x] Removed comment from Form.changed_data; refs #24191

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"cccb7b49dc2bfdbebae170ebfeee1abf2a731552" cccb7b49]:
 {{{
 #!CommitTicketReference repository=""
 revision="cccb7b49dc2bfdbebae170ebfeee1abf2a731552"
 [1.8.x] Fixed #24191 -- Documented Form.changed_data

 Thanks rhertzog and Björn Påhlsson for the suggestion.

 Backport of 5c98223f39e5cf92c603a08e7ed70d57e565a5a3 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.316fa8fb827ebf3284b2eda14a203f1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"5c98223f39e5cf92c603a08e7ed70d57e565a5a3" 5c98223]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c98223f39e5cf92c603a08e7ed70d57e565a5a3"
 Fixed #24191 -- Documented Form.changed_data

 Thanks rhertzog and Björn Påhlsson for the suggestion.
 }}}

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"5987b3c46d5a6948737627d294d95ed54d49eae6" 5987b3c]:
 {{{
 #!CommitTicketReference repository=""
 revision="5987b3c46d5a6948737627d294d95ed54d49eae6"
 Removed comment from Form.changed_data; refs #24191
 }}}

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

Re: [Django] #24421: Querying a reverse ForeignObject relation using exclude() fails

[Django]

#24421: Querying a reverse ForeignObject relation using exclude() fails
-+-
 Reporter:  animan1  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignObject,   | Triage Stage:  Accepted
  MySQL, SQLite  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by joeri):

 I added some comments on what's happening. The whole generated query for
 an exclude seems incorrect or incomplete.

 {{{
 def test_reverse_query(self):
 membership =
 Membership.objects.create(membership_country=self.usa, person=self.bob,
 group=self.cia)

 # The following query is generated for a filter:
 #
 # SELECT ... FROM "foreign_object_group" INNER JOIN
 "foreign_object_membership" ON (
 #   "foreign_object_group"."group_country_id" =
 "foreign_object_membership"."membership_country_id" AND
 #   "foreign_object_group"."id" =
 "foreign_object_membership"."group_id"
 # ) WHERE "foreign_object_membership"."id" = 1 ORDER BY
 "foreign_object_group"."name" ASC

 self.assertQuerysetEqual(
 Group.objects.filter(membership=membership),
 ['']
 )
 # The following query is generated for an exclude:
 #
 # SELECT ... FROM "foreign_object_group" WHERE NOT (
 #   "foreign_object_group"."group_country_id" IN (
 #   SELECT U1."membership_country_id" AS Col1, U1."group_id"
 AS Col2 FROM "foreign_object_membership" U1 WHERE U1."id" = 1
 #   )
 # ) ORDER BY "foreign_object_group"."name" ASC

 # The error by SQLite:
 # OperationalError: only a single result allowed for a SELECT that
 is part of an expression

 self.assertQuerysetEqual(
 Group.objects.exclude(membership=membership),
 []
 )

 }}}

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

Re: [Django] #24901: makemigrations should create empty migrations dir for any installed app without it

[Django]

#24901: makemigrations should create empty migrations dir for any installed app
without it
-+-
 Reporter:  coldmind |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Accepted => Someday/Maybe


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

Re: [Django] #24912: prefetch_related fails with sqlite3 database and UUIDField primary keys

[Django]

#24912: prefetch_related fails with sqlite3 database and UUIDField primary keys
-+-
 Reporter:  brki |Owner:  brki
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField| Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by brki):

 * stage:  Accepted => Ready for checkin


Comment:

 There's a pull request open with a fix for this:
 https://github.com/django/django/pull/4782.

 It was failing before with at least sqlite and mysql.

 The fix was tested on sqlite, mysql and postgresql.

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

Re: [Django] #24908: Overridden field in modelform used in modeladmin which name is returned by get_readonly_fields

[Django]

#24908: Overridden field in modelform used in modeladmin which name is returned 
by
get_readonly_fields
---+
 Reporter:  jpic   |Owner:
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 dgouldin):

 * owner:  dgouldin =>
 * status:  assigned => new


Comment:

 Oops, just realized there's already a PR for this. Ignore me.

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

Re: [Django] #24908: Overridden field in modelform used in modeladmin which name is returned by get_readonly_fields

[Django]

#24908: Overridden field in modelform used in modeladmin which name is returned 
by
get_readonly_fields
---+
 Reporter:  jpic   |Owner:  dgouldin
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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 dgouldin):

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


Comment:

 Looks like this is happening because `ModelFormMetaclass.__new__` doesn't
 expect the form class's declared fields to also be in its exclude opts.
 Normally, that would be a reasonable assumption. (Why would you exclude a
 field you've bothered to explicitly deeclared?) But in this case, it's the
 admin which is excluding the field, so the assumption breaks. Patch
 coming.

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

[Django] #24926: text improvement request for deployment guide

[Django]

#24926: text improvement request for deployment guide
--+
 Reporter:  JorisBenschop |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 The current text on deployment
 ([https://docs.djangoproject.com/en/dev/howto/deployment/]) says:
 > Django’s chock-full of shortcuts to make Web developer’s lives easier,
 but all those tools are of
 > no use if you can’t easily deploy your sites. Since Django’s inception,
 ease of deployment
 > has been a major goal. There’s a number of good ways to easily deploy
 Django:
 > How to deploy with WSGI
 > Deployment checklist

 Its a bit strange to state "a number of good '''ways'''", and then present
 the reader with exactly one method. Ideally I'd like to see a suggestion
 to host multiple sites one one server without weird tricks, but at least
 it may be good to indicate there is ony a single method recommended to
 deploy when there is indeed only one method... so maybee like this:

 > Django’s chock-full of shortcuts to make Web developer’s lives easier,
 but all those tools are of
 > no use if you can’t easily deploy your sites. Since Django’s inception,
 ease of deployment
 > has been a major goal. THe best way to deploy Django is through WSGI:
 > How to deploy with WSGI
 > Deployment checklist

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

Re: [Django] #24728: feedgenerator classes still use "mime_type" instead of "content_type"

[Django]

#24728: feedgenerator classes still use "mime_type" instead of "content_type"
-+-
 Reporter:  yourcelf |Owner:  raphaelm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"5c125f63f77e169a459c11bab0f639c83fabc6e2" 5c125f6]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c125f63f77e169a459c11bab0f639c83fabc6e2"
 Fixed #24728 -- Renamed mime_type to content_type for syndication feeds

 Renamed the mime_type properties of RssFeed and Atom1Feed to
 content_type and start deprecation for the old names.
 }}}

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

Re: [Django] #24924: Incorrect Join Promotion with Annotations

[Django]

#24924: Incorrect Join Promotion with Annotations
---+--
 Reporter:  mlavin |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.8
 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 robline):

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


Comment:

 Attached a test case that fails because of this issue.
 {{{

 $ python runtests.py expressions_case
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 ..F.s...
 ==
 FAIL: test_join_promotion_with_multiple_annotations
 (expressions_case.tests.CaseExpressionTests)
 --
 Traceback (most recent call last):
   File "/home/rob/rob/caktus/django/tests/expressions_case/tests.py", line
 1073, in test_join_promotion_with_multiple_annotations
 lambda x: (x, x.foo, x.bar)
   File "/home/rob/rob/caktus/django/django/test/testcases.py", line 932,
 in assertQuerysetEqual
 return self.assertEqual(list(items), values, msg=msg)
 AssertionError: Lists differ: [] != [(, 3, 5)]

 Second list contains 1 additional elements.
 First extra element 0:
 (, 3, 5)

 - []
 + [(, 3, 5)]

 --
 Ran 76 tests in 0.172s

 FAILED (failures=1, skipped=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 }}}

 The query returns an empty list because of the inner join.

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

Re: [Django] #24924: Incorrect Join Promotion with Annotations

[Django]

#24924: Incorrect Join Promotion with Annotations
---+
 Reporter:  mlavin |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by robline):

 * Attachment "24924.diff" added.

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

Re: [Django] #24899: Split up migrations autodetector._detect_changes into separate functions

[Django]

#24899: Split up migrations autodetector._detect_changes into separate functions
-+-
 Reporter:  MarkusH  |Owner:
 Type:   |  iamsteadman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  afraid-to-commit | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by MarkusH):

 Yes, that's exactly what I had in mind. Thank you.

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

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 charettes):

 Does `len(self.source_expressions) == (c.source_expressions)` in all
 cases? If that's the case maybe we should loop over all
 `c.source_expressions` to test for `.contains_aggregate and not
 summarize`.

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

Re: [Django] #24925: Coalesce converts datetime to string on MySQL

[Django]

#24925: Coalesce converts datetime to string on MySQL
-+-
 Reporter:  Ian-Foote|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 Ian-Foote):

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


Comment:

 A workaround for this is to `cast` the python datetime value to a MySQL
 datetime using `RawSQL`: `RawSQL("cast(%s as datetime)", (datetime,))`.

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

Re: [Django] #22728: get_or_create with field lookups cause empty values

[Django]

#22728: get_or_create with field lookups cause empty values
-+-
 Reporter:  Xudonax  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  get_or_create| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

 * needs_better_patch:  1 => 0


Comment:

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

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 mcbhenwood):

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 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 mcbhenwood):

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

[Django] #24925: Coalesce converts datetime to string on MySQL

[Django]

#24925: Coalesce converts datetime to string on MySQL
--+
 Reporter:  Ian-Foote |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Passing a `datetime` to `Coalesce` leads to a string `annotation` instead
 of a `datetime`.

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

Re: [Django] #24902: Unapply squashed migration when any of the individual migrations are unapplied

[Django]

#24902: Unapply squashed migration when any of the individual migrations are
unapplied
+
 Reporter:  MarkusH |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  invalid
 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 carljm):

 That's fine, though I think we'll end up wanting to do this anyway if/when
 #24900 is implemented.

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  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
---+

Comment (by alasdairnicol):

 Replying to [comment:4 timgraham]:
 > Let's remove that comment in the code then. Same PR separate commit
 would be fine.

 I've added another commit to the pull request that removes the comment.

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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
-+-

Comment (by mcbhenwood):

 Pull Request: https://github.com/django/django/pull/4775

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

Re: [Django] #22561: EmailMessage should respect RFC2822 on max line length

[Django]

#22561: EmailMessage should respect RFC2822 on max line length
-+-
 Reporter:  notsqrt  |Owner:  levkowetz
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.6
 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 levkowetz):

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

Re: [Django] #24923: Aggregates in order_by should error out nicely

[Django]

#24923: Aggregates in order_by should error out nicely
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * version:  1.8 => master


Comment:

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

Re: [Django] #19542: Testing with Oracle: mirror databases do not work

[Django]

#19542: Testing with Oracle: mirror databases do not work
---+
 Reporter:  shai   |Owner:  shaib
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  oracle | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by shaib):

 * Attachment "test_mirroring.tgz" added.

 A simple project which can be used to test that mirroring works in
 testing. You will need to change credentials, of course.

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

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
-+-
 Reporter:  gannetson|Owner:  gannetson
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | 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 gannetson):

 Do you mean this one?
 
https://github.com/gannetson/django/commit/fcb527df09a8087763725e123255eebca2474e76

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

Re: [Django] #24474: Make display for null fields in Django admin configurable through settings

[Django]

#24474: Make display for null fields in Django admin configurable through 
settings
-+-
 Reporter:  gannetson|Owner:  gannetson
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | 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):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, pending a cosmetic comment.

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

Re: [Django] #4960: Add "strip" keyword argument to CharField constructor

[Django]

#4960: Add "strip" keyword argument to CharField constructor
-+--
 Reporter:  tzellman@…   |Owner:  danielward
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CharField strip  | 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:

 I guess you missed the more extensive
 [https://github.com/django/django/pull/4059 pull request] that was already
 proposed. It still needs some improvements.

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

[Django] #24924: Incorrect Join Promotion with Annotations

[Django]

#24924: Incorrect Join Promotion with Annotations
---+
 Reporter:  mlavin |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 This was originally addressed in #24766 and released in 1.8.2 but as noted
 here https://code.djangoproject.com/ticket/24766#comment:7 this problem
 still exists if there are multiple annotations. Working on a failing 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/049.8002427e01fd091dcc3a0b4e9d095aa7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24922: Templates: conflicting settings should emit a system check error

[Django]

#24922: Templates: conflicting settings should emit a system check error
-+-
 Reporter:  sergei-maertens  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  templates, system| Triage Stage:  Accepted
  check  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by sergei-maertens):

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

Re: [Django] #24728: feedgenerator classes still use "mime_type" instead of "content_type"

[Django]

#24728: feedgenerator classes still use "mime_type" instead of "content_type"
-+-
 Reporter:  yourcelf |Owner:  raphaelm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | 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):

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

Re: [Django] #24316: Admin changelist column CSS classes do not use short description, instead using str(list_display_function)

[Django]

#24316: Admin changelist column CSS classes do not use short description, 
instead
using str(list_display_function)
---+
 Reporter:  JordanBright   |Owner:
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 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 argaen):

 * Attachment "24316_test_case_1.diff" added.

 New TestCase since previous one was passing 2 asserts that it shouldn't

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

Re: [Django] #24779: django-1.8.1 fails test with pypy - FAIL: test_serialize_datetime_safe (migrations.test_writer.WriterTests)

[Django]

#24779: django-1.8.1 fails test with pypy - FAIL: test_serialize_datetime_safe
(migrations.test_writer.WriterTests)
+
 Reporter:  jlec|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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
+

Comment (by flupzor):

 I've discovered the problem, I think it's a bug in PyPy. But I don't know
 if there is any Python API specification where this is specified in.

 The difference lies in the way the `__repr__` is made for date, time and
 datetime classes.

 In pypy the `__repr__` is determined as follows:

 date:
 
https://bitbucket.org/pypy/pypy/src/5d676752ae6613d0b423f4c1028ac47e1571d5fa/lib_pypy/datetime.py?at=default#cl-790
 time:
 
https://bitbucket.org/pypy/pypy/src/5d676752ae6613d0b423f4c1028ac47e1571d5fa/lib_pypy/datetime.py?at=default#cl-1281
 datetime:
 
https://bitbucket.org/pypy/pypy/src/5d676752ae6613d0b423f4c1028ac47e1571d5fa/lib_pypy/datetime.py?at=default#cl-1692

 While in cpython it is done like this:

 date:
 https://github.com/python/cpython/blob/master/Modules/_datetimemodule.c#L2633
 time:
 https://github.com/python/cpython/blob/master/Modules/_datetimemodule.c#L3581
 datetime:
 https://github.com/python/cpython/blob/master/Modules/_datetimemodule.c#L4442

 Which causes the date, datetime and time classes in datetime_safe module
 to return the wrong __repr__ value.

 e.g. in cpython 2 and 3 repr(datetime_safe.date(2015, 1, 1)) would return:
 date(2015, 1, 1)

 While in pypy this would return:
 datetime.date(2015, 1, 1)

 And the same would happen for datetime and time.

 There are three solutions I can think of:

 - Override the ` __repr__` function in datetime_safe.{date,time,datetime}
 which return the representation consistently for both PyPy and cpython.
 - Make an hard "if PyPy" condition and then don't prepend the 'datetime'
 in that case (this would be the ugly solution imo)
 - Fix it in PyPy.

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

Re: [Django] #24901: makemigrations should create empty migrations dir for any installed app without it

[Django]

#24901: makemigrations should create empty migrations dir for any installed app
without it
--+
 Reporter:  coldmind  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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
--+

Comment (by coldmind):

 After discussion with Markus, we should postpone this until the result of
 #24481

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  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
---+

Comment (by timgraham):

 Let's remove that comment in the code then. Same PR separate commit would
 be fine.

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

Re: [Django] #20825: Make cookies use the HTTPOnly flag by default

[Django]

#20825: Make cookies use the HTTPOnly flag by default
---+
 Reporter:  julien |Owner:  julien
 Type:  New feature|   Status:  closed
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 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 erikr):

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


Comment:

 I completely concur. For the `set_cookie` default, I do see a security
 benefit, but I feel it's so small that it's not worth breaking the
 backwards compatibility. Especially when considering that this is likely
 to break things silently, and not be noticed in unit tests - only by vague
 error reports from users.

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

Re: [Django] #24890: Add warning to collectstatic when static files have clashing names

[Django]

#24890: Add warning to collectstatic when static files have clashing names
-+-
 Reporter:  giuliettamasina  |Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  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 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/073.3eec352f6c5aebaa4c4cd83872c2a497%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24906: ResolverMatch.app_name doesn't contain full application namespace for nested namespaces

[Django]

#24906: ResolverMatch.app_name doesn't contain full application namespace for
nested namespaces
-+
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  1.8
 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 knbk):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/4771

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

Re: [Django] #24829: TemplateView raises unhandled ContentNotRenderedError error when used as error handler

[Django]

#24829: TemplateView raises unhandled ContentNotRenderedError error when used as
error handler
---+--
 Reporter:  nonZero|Owner:  ana-balica
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  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 ana-balica):

 * status:  new => assigned
 * owner:  nobody => ana-balica


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

Re: [Django] #19542: Testing with Oracle: mirror databases do not work

[Django]

#19542: Testing with Oracle: mirror databases do not work
---+
 Reporter:  shai   |Owner:  shaib
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  oracle | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by shaib):

 * status:  new => assigned
 * owner:  nobody => shaib
 * has_patch:  0 => 1
 * version:  1.4 => 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/062.80922db0954eef6145f049a7080ba72b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  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 alasdairnicol):

 * cc: alasdair@… (added)
 * 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.b65d553790615a1b39ec84b7e1b40c00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 coldmind):

 I think it because
 
https://github.com/django/django/blob/3e9b5bfd9c3e16c968278f7d050f52739690eb29/django/db/models/aggregates.py#L21
 is using only first expression, so it will be confusing to allow passing
 more

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

Re: [Django] #20825: Make cookies use the HTTPOnly flag by default

[Django]

#20825: Make cookies use the HTTPOnly flag by default
---+
 Reporter:  julien |Owner:  julien
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.5
 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
---+

Comment (by raphaelm):

 Actually, accessing the CSRF cookie via JavaScript is the recommended way
 to use the CSRF protection with AJAX (see:
 https://docs.djangoproject.com/en/1.8/ref/csrf/#ajax). So, as far as the
 CSRF cookie is concerned, I'd close this as "wontfix".

 As for set_cookie, this would break backwards compatibility and as the
 most important cookie, the sessison cookie, is protected, I'd also vote
 for wontfix here. Any other opinions?

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

Re: [Django] #24191: form.changed_data appears to be undocumented

[Django]

#24191: form.changed_data appears to be undocumented
---+
 Reporter:  rhertzog   |Owner:  nobody
 Type:  New feature|   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
---+

Comment (by alasdairnicol):

 I have created a pull request https://github.com/django/django/pull/4768
 which documents form.changed_data.

 I haven't addressed the comment that tim refers to. Changing the
 implementation of ``has_changed`` to use a hidden field would have
 backwards incompatibility implications for `form.has_changed()` (which is
 documented) as well.

 I may have misunderstood the suggestion in the comments, but am not sure
 that the the hidden field approach is better. Not every form is
 instantiated from a `request.POST` or request.GET that contains a hidden
 field.

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

Re: [Django] #24899: Split up migrations autodetector._detect_changes into separate functions

[Django]

#24899: Split up migrations autodetector._detect_changes into separate functions
-+-
 Reporter:  MarkusH  |Owner:
 Type:   |  iamsteadman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  afraid-to-commit | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Markus, please confirm [https://github.com/django/django/pull/4759 PR] is
 what you had in mind.

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

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 gchp):

 * has_patch:  0 => 1


Comment:

 PR here: https://github.com/django/django/pull/4767

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

Re: [Django] #24744: Missing relabeled_clone methods are causing fails in subqueries

[Django]

#24744: Missing relabeled_clone methods are causing fails in subqueries
--+
 Reporter:  mrAdm |Owner:  coldmind
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Release blocker   |   Resolution:
 Keywords:  hstore| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by coldmind):

 After several discussions we decided to not making base mixins for now,
 because it is not so simple formalize common things for all
 transfroms/functions/aggregates/etc, so I fixed the actual problem.

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

Re: [Django] #24744: Missing relabeled_clone methods are causing fails in subqueries

[Django]

#24744: Missing relabeled_clone methods are causing fails in subqueries
--+
 Reporter:  mrAdm |Owner:  coldmind
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Release blocker   |   Resolution:
 Keywords:  hstore| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by coldmind):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #23516: ifchanged no longer works within an included template

[Django]

#23516: ifchanged no longer works within an included template
-+
 Reporter:  dracos   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.7
 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 dracos):

 * has_patch:  0 => 1


Comment:

 I have submitted a PR at https://github.com/django/django/pull/4753 with
 comments outlined there, reworked to use render_context as suggested.

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

Re: [Django] #24912: prefetch_related fails with sqlite3 database and UUIDField primary keys

[Django]

#24912: prefetch_related fails with sqlite3 database and UUIDField primary keys
-+-
 Reporter:  brki |Owner:  brki
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by brki):

 * status:  new => assigned
 * owner:   => brki


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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 mcbhenwood):

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

Re: [Django] #24923: Aggregates in order_by should error out nicely

[Django]

#24923: Aggregates in order_by should error out nicely
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 zedr):

 * owner:  zedr =>
 * status:  assigned => new


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

Re: [Django] #24923: Aggregates in order_by should error out nicely

[Django]

#24923: Aggregates in order_by should error out nicely
-+-
 Reporter:  akaariai |Owner:  zedr
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 zedr):

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


Comment:

 akaariai: what would you suggest as the error message or behaviour?

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

Re: [Django] #10852: Add no-fuzzy-matching option to makemessages

[Django]

#10852: Add no-fuzzy-matching option to makemessages
-+-
 Reporter:  graham.carlyle@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by sergeykolosov):

 Those still looking for an option to customise `msgmerge` arguments, have
 a look at changes introduced in
 
https://github.com/django/django/commit/06efeae598c6dafbe56d2ea323a0dccdd5bf2b8e
 (Django 1.7 and above); now it is feasible by subclassing the
 `makemessages` command, and overriding `msgmerge_options`.

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

Re: [Django] #24922: Templates: conflicting settings should emit a system check error

[Django]

#24922: Templates: conflicting settings should emit a system check error
-+-
 Reporter:  sergei-maertens  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  templates, system| Triage Stage:  Accepted
  check  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by raphaelm):

 * stage:  Unreviewed => Accepted


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.b541d06ee70c086632923d538148de74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by akaariai):

 This should be one-line change to django/db/models/aggregates, remove the
 line that does the assert for len(self.source_expressions) and things
 should work.

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

Re: [Django] #24912: prefetch_related fails with sqlite3 database and UUIDField primary keys

[Django]

#24912: prefetch_related fails with sqlite3 database and UUIDField primary keys
-+-
 Reporter:  brki |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by zedr):

 * status:  assigned => new
 * owner:  zedr =>


Comment:

 With your fix:

 {{{(0.000) QUERY = 'SELECT "model_fields_player"."id",
 "model_fields_player"."name" FROM "model_fields_player" WHERE
 "model_fields_player"."id" = %s' - PARAMS =
 ('8aa7fd54d3d24c7bbca418a584fc44c9',);
 args=('8aa7fd54d3d24c7bbca418a584fc44c9',)

 (0.000) QUERY = 'SELECT ("model_fields_player_awards"."player_id") AS
 "_prefetch_related_val_player_id", "model_fields_award"."id",
 "model_fields_award"."name" FROM "model_fields_award" INNER JOIN
 "model_fields_player_awards" ON ( "model_fields_award"."id" =
 "model_fields_player_awards"."award_id" ) WHERE
 "model_fields_player_awards"."player_id" IN (%s)' - PARAMS =
 ('8aa7fd54d3d24c7bbca418a584fc44c9',);
 args=('8aa7fd54d3d24c7bbca418a584fc44c9',)}}}

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by tricoder42):

 I've found that commit too
 https://code.djangoproject.com/ticket/24080#comment:7, but don't know how
 to fix it. It seems it's related to python version on OS X

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

Re: [Django] #24922: Templates: conflicting settings should emit a system check error

[Django]

#24922: Templates: conflicting settings should emit a system check error
-+-
 Reporter:  sergei-maertens  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  templates, system| Triage Stage:
  check  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by sergei-maertens:

Old description:

> I discovered that specifying the templates settings as following, raises
> an error when rendering the template:
>
> {{{#!python
> TEMPLATES = [
> {
> 'BACKEND': 'django.template.backends.django.DjangoTemplates',
> 'DIRS': [],
> 'APP_DIRS': True,
> 'OPTIONS': {
> 'context_processors': [
> 'django.template.context_processors.debug',
> 'django.template.context_processors.request',
> 'django.contrib.auth.context_processors.auth',
> 'django.contrib.messages.context_processors.messages',
> ],
> },
> 'loaders': [
> ('django.template.loaders.cached.Loader', [
> 'django.template.loaders.filesystem.Loader',
> 'django.template.loaders.app_directories.Loader',
> ]),
> ],
> },
> ]
> }}}
>
> Error:
> {{{
> Traceback (most recent call last):
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/core/handlers/wsgi.py", line 189, in __call__
> response = self.get_response(request)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/core/handlers/base.py", line 218, in get_response
> response = self.handle_uncaught_exception(request, resolver,
> sys.exc_info())
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/core/handlers/base.py", line 268, in
> handle_uncaught_exception
> return callback(request, **param_dict)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/utils/decorators.py", line 110, in _wrapped_view
> response = view_func(request, *args, **kwargs)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/views/defaults.py", line 42, in server_error
> template = loader.get_template(template_name)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/loader.py", line 29, in get_template
> engines = _engine_list(using)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/loader.py", line 144, in _engine_list
> return engines.all() if using is None else [engines[using]]
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/utils.py", line 110, in all
> return [self[alias] for alias in self]
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/utils.py", line 101, in __getitem__
> engine = engine_cls(params)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/backends/django.py", line 24, in __init__
> self.engine = Engine(self.dirs, self.app_dirs, **options)
>   File "/home/modelbrouw/.virtualenvs/staging/lib/python2.7/site-
> packages/django/template/engine.py", line 36, in __init__
> "app_dirs must not be set when loaders is defined.")
> django.core.exceptions.ImproperlyConfigured: app_dirs must not be set
> when loaders is defined.
> }}}

New description:

 I discovered that specifying the templates settings as following, raises
 an error when rendering the template:

 {{{#!python
 TEMPLATES = [
 {
 'BACKEND': 'django.template.backends.django.DjangoTemplates',
 'DIRS': [os.path.join(BASE_DIR, 'templates')],
 'APP_DIRS': True,
 'OPTIONS': {
 'context_processors': [
 'django.template.context_processors.debug',
 'django.template.context_processors.request',
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 ],
 'loaders': [
 ('django.template.loaders.cached.Loader', [
 'django.template.loaders.filesystem.Loader',
 'django.template.loaders.app_directories.Loader',
 ]),
 

Re: [Django] #24859: UUIDField does not validate query value

[Django]

#24859: UUIDField does not validate query value
-+-
 Reporter:  cancan101|Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by iamsteadman):

 * owner:  iamsteadman =>
 * status:  assigned => new


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

Re: [Django] #24916: DjangoJSONEncoder: Decimal type localization mechanism is missing

[Django]

#24916: DjangoJSONEncoder: Decimal type localization mechanism is missing
-+-
 Reporter:  vartagg  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core |  Version:  1.8
  (Serialization)|
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by vartagg):

 The JSON standard for serializing decimal values does not provide for
 localized formatting. (See JSON.org.) This is why values are not
 localized. I think it would also make the date less portable across
 locales.

 By following this, support of Decimals in DjangoJSONEncoder makes sense
 only for web-applications that don't use localizations.

  If you need localized values, then I'd suggest to create a custom encoder
 for your serializer of choice which outputs the decimals appropriately.

 Ok, but DjangoJSONEncoder has only one method: "default", what making it
 hard to override. How about to divide it to different methods? It would be
 very helpful.

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

[Django]

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by gchp):

 Did some git bisecting, and found the commit which introduced this issue:
 
https://github.com/django/django/commit/da9fe5c717c179a9e881a40efd3bfe36a21bf4a6

 Investigating a fix now, but not 100% sure on what's going on. Commenting
 out the calls to these two methods prevents the segfault, but triggers a
 whole ton of other issues:
 https://github.com/gchp/django/blob/master/django/test/testcases.py#L967-L981

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

Re: [Django] #24859: UUIDField does not validate query value

[Django]

#24859: UUIDField does not validate query value
-+-
 Reporter:  cancan101|Owner:
 Type:   |  iamsteadman
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by iamsteadman):

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