Re: [Django] #23890: Deprecation warning with numpy 1.8+

[Django]

#23890: Deprecation warning with numpy 1.8+
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"a917a5601f145042f31d0e2011bc41c2a3aaea7c" a917a560]:
 {{{
 #!CommitTicketReference repository=""
 revision="a917a5601f145042f31d0e2011bc41c2a3aaea7c"
 Refs #23890 -- Removed numpy deprecation warning silencing.

 Obsolete since numpy 1.12.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/067.334c2d178ed617ac6a35e14a445fe66c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29335: changed default pastebin link to dpaste.de

[Django]

#29335: changed default pastebin link to dpaste.de
-+-
 Reporter:  Malik A. Rumi|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Error reporting  |  Version:  2.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  pastebin, dpaste | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  contrib.admin => Error reporting


Comment:

 I don't understand the benefit of the proposed change. The topic for
 #django says "do not use pastebin.com!" -- which is different from
 dpaste.com that the debug page uses. Anyway, a proposal like this is more
 suited for the DevelopersMailingList.

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

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin

[Django]

#29122: Add a better font for Persian/Farsi to the admin
-+-
 Reporter:  Mohammad Hossein |Owner:  Kelly
  Mojtahedi  |  Hogan
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Persian, font,   | Triage Stage:
  Farsi  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tim Graham):

 Hi Kelly, I think it's a bit premature to assign the ticket as it has
 "someday/maybe" status. The first step is to propose a solution (if a
 change in Django needs to be made at all) on the DevelopersMailingList as
 I suggested in comment 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/065.899cc60509f1a7b778dee92c7b6fa407%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29338: Can't use OuterRef in union Subquery

[Django]

#29338: Can't use OuterRef in union Subquery
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham):

 Are you sure that generating some sensible SQL for this queryset is
 possible?

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

Re: [Django] #3006: generic relations do not act as expected in a filter/get

[Django]

#3006: generic relations do not act as expected in a filter/get
-+-
 Reporter:  jeroen_at_lbvd.nl|Owner:  Robert
 |  Myers
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  generic relations| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Feel free to continue the [https://groups.google.com/d/topic/django-
 developers/bCUDl7MlkOA/discussion discussion on django-developers] if
 there's some motivation for this.

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

[Django] #29338: Can't use OuterRef in union Subquery

[Django]

#29338: Can't use OuterRef in union Subquery
-+-
   Reporter:  Matthew|  Owner:  nobody
  Pava   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  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  |
-+-
 When you make a QuerySet using the `union` method or the `|` operator, the
 QuerySet passed into the `union` method cannot reference `OuterRef` even
 when wrapped with `Subquery`.

 For example:

 {{{
 cls = Document.objects.filter(
 checklist__isnull=False,
 part=OuterRef('id')
 ).values('checklist__customer', 'created')

 ots = Document.objects.filter(
 ownershiptransfer__isnull=False,
 part=OuterRef('id')
 ).values('ownershiptransfer__ship_target__contact', 'created')

 return self.annotate(
 owner=Subquery(cls.union(ots).values('owner')[:1])
 )
 }}}


 Returns this error:

 {{{
 ValueError
 This queryset contains a reference to an outer query and may only be used
 in a subquery.

 }}}

 I get the same error with this statement:

 {{{
 return self.annotate(
 owner=Subquery((cls | ots).values('owner')[:1])
 )

 }}}

 (As an aside, I also get an error when I try to apply an `order_by`
 clause.)

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

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin

[Django]

#29122: Add a better font for Persian/Farsi to the admin
-+-
 Reporter:  Mohammad Hossein |Owner:  Kelly
  Mojtahedi  |  Hogan
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Persian, font,   | Triage Stage:
  Farsi  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Kelly Hogan):

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

Re: [Django] #3006: generic relations do not act as expected in a filter/get

[Django]

#3006: generic relations do not act as expected in a filter/get
-+-
 Reporter:  jeroen_at_lbvd.nl|Owner:  Robert
 |  Myers
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  generic relations| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I'd lean toward a wontfix. In particular, making changes in
 `django/db/models/sql/query.py` for a contrib app doesn't look like a good
 separation of concerns. Is there a downside to the alternative of adding
 the `GenericRelation`?

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

Re: [Django] #27629: Inconsistent check of allow_relation in ForwardManyToOneDescriptor.__set__

[Django]

#27629: Inconsistent check of allow_relation in 
ForwardManyToOneDescriptor.__set__
-+-
 Reporter:  Sven Coenye  |Owner:  Stefan R.
 |  Filipek
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  allow_relation   | Triage Stage:  Accepted
  ForwardManyToOneDescriptor |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

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

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Daniel Miller):

 It's now been refactored to not use `extra_tables`, and there is a secret
 (undocumented, experimental API) way to do a left outer 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/067.498da5af1739419975bc5261adab77f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29337: __len__ & __bool__ support in RawQueryset

[Django]

#29337: __len__ & __bool__ support in RawQueryset
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
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 Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Follow on from #28600

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

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 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 Carlton Gibson):

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

Re: [Django] #3006: generic relations do not act as expected in a filter/get

[Django]

#3006: generic relations do not act as expected in a filter/get
-+-
 Reporter:  jeroen_at_lbvd.nl|Owner:  Robert
 |  Myers
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  generic relations| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch looks good. Not 100% sure it's needed given `GenericRelation` is
 already available.

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

Re: [Django] #29303: non_atomic_requests decorator alters _non_atomic_requests attribute of original function

[Django]

#29303: non_atomic_requests decorator alters _non_atomic_requests attribute of
original function
-+-
 Reporter:  Alasdair Nicol   |Owner:  Windson
 |  yang
 Type:  Bug  |   Status:  assigned
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 Windson yang):

 * status:  new => assigned
 * owner:  nobody => Windson yang


Comment:

 I'm not sure how to fix this, as we can see, in _non_atomic_requests
 method we add 'using' in the original view then return it. That is why
 my_view._non_atomic_requests changed. The first solution will copy a new
 view from the old one and return the new view. The second will be we make
 the document more clear about this behavior.

 {{{
 def _non_atomic_requests(view, using):
 try:
 view._non_atomic_requests.add(using)
 except AttributeError:
 view._non_atomic_requests = {using}
 return view


 def non_atomic_requests(using=None):
 if callable(using):
 return _non_atomic_requests(using, DEFAULT_DB_ALIAS)
 else:
 if using is None:
 using = DEFAULT_DB_ALIAS
 return lambda view: _non_atomic_requests(view, using)
 }}}

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

Re: [Django] #29336: No docs for circular inheritance

[Django]

#29336: No docs for circular inheritance
-+-
 Reporter:  Adrian Turjak|Owner:  Adrian
 Type:   |  Turjak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 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 Carlton Gibson):

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


Comment:

 This would make a good addition to the
 [https://docs.djangoproject.com/en/2.0/howto/overriding-templates/
 Overriding Templates How-To].

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

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

[Django]

#29174: makemessages does not find translations in Python 3.6 formatted string
literals
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 Severity:  Normal|   Resolution:  fixed
 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 Carlton Gibson ):

 In [changeset:"a5d1fe59c59fa716918b6cec5e8ab747720b74fc" a5d1fe5]:
 {{{
 #!CommitTicketReference repository=""
 revision="a5d1fe59c59fa716918b6cec5e8ab747720b74fc"
 Revert "[1.11.x] Fixed #29174, #29175 -- Doc'd that f-strings and
 JavaScript template strings can't be translated."

 This reverts commit 8b4798c8d31b3cd9faab4caf11fca000b07f0181.
 }}}

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

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

[Django]

#29175: makemessages doesn't parse ES6 template strings
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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 Carlton Gibson ):

 In [changeset:"a5d1fe59c59fa716918b6cec5e8ab747720b74fc" a5d1fe5]:
 {{{
 #!CommitTicketReference repository=""
 revision="a5d1fe59c59fa716918b6cec5e8ab747720b74fc"
 Revert "[1.11.x] Fixed #29174, #29175 -- Doc'd that f-strings and
 JavaScript template strings can't be translated."

 This reverts commit 8b4798c8d31b3cd9faab4caf11fca000b07f0181.
 }}}

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

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

[Django]

#29175: makemessages doesn't parse ES6 template strings
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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 Carlton Gibson ):

 In [changeset:"0d2ec8db483a900c27b8fada30688ef8f25cecfa" 0d2ec8d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d2ec8db483a900c27b8fada30688ef8f25cecfa"
 [2.0.x] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript
 template strings can't be translated.

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

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

[Django]

#29174: makemessages does not find translations in Python 3.6 formatted string
literals
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 Severity:  Normal|   Resolution:  fixed
 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 Carlton Gibson ):

 In [changeset:"0d2ec8db483a900c27b8fada30688ef8f25cecfa" 0d2ec8d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d2ec8db483a900c27b8fada30688ef8f25cecfa"
 [2.0.x] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript
 template strings can't be translated.

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

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

[Django]

#29175: makemessages doesn't parse ES6 template strings
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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 Carlton Gibson ):

 In [changeset:"8b4798c8d31b3cd9faab4caf11fca000b07f0181" 8b4798c]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b4798c8d31b3cd9faab4caf11fca000b07f0181"
 [1.11.x] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript
 template strings can't be translated.

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

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

[Django]

#29174: makemessages does not find translations in Python 3.6 formatted string
literals
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 Severity:  Normal|   Resolution:  fixed
 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 Carlton Gibson ):

 In [changeset:"8b4798c8d31b3cd9faab4caf11fca000b07f0181" 8b4798c]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b4798c8d31b3cd9faab4caf11fca000b07f0181"
 [1.11.x] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript
 template strings can't be translated.

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

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

[Django]

#29175: makemessages doesn't parse ES6 template strings
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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 Carlton Gibson ):

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


Comment:

 In [changeset:"c3437f734d03d93f798151f712064394652cabed" c3437f73]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3437f734d03d93f798151f712064394652cabed"
 Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript template
 strings can't be translated.
 }}}

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

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

[Django]

#29174: makemessages does not find translations in Python 3.6 formatted string
literals
--+
 Reporter:  Artem Skoretskiy  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 Severity:  Normal|   Resolution:  fixed
 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 Carlton Gibson ):

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


Comment:

 In [changeset:"c3437f734d03d93f798151f712064394652cabed" c3437f73]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3437f734d03d93f798151f712064394652cabed"
 Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript template
 strings can't be translated.
 }}}

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

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
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 Adnan Umer):

 * needs_docs:  1 => 0


Comment:

 Unchecking "Needs Documentation" to have PR reviewed again after doing
 requested changes.

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

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

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adnan Umer):

 Replying to [comment:20 Carlton Gibson]:
 > Did that happen? (I
 [https://github.com/django/django/pulls?utf8=✓=is%3Apr+author%3Auadnan
 can't see another PR by Adnan])
 I havn't yet opened any new PR for that. I was just waiting on
 approval/merge of my existing ticket. Once that is done I'll create a new
 PR for that.


 > I ask because the warning in
 
[https://github.com/django/django/blob/7a22d9f75125e3cfbea0979a876efe4634f6fe05/docs/topics/db/sql.txt#L88-L97
 docs/db/sql.txt] about this will also need updating:

 Yes, I've created a new ticket https://code.djangoproject.com/ticket/29337
 and assigned that to myself. Not sure should I open PR once this one got
 merged or before merge?

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

Re: [Django] #29337: __len__ & __bool__ support in RawQueryset

[Django]

#29337: __len__ & __bool__ support in RawQueryset
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 Adnan Umer):

 * status:  new => assigned
 * owner:  nobody => Adnan Umer


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

[Django] #29337: __len__ & __bool__ support in RawQueryset

[Django]

#29337: __len__ & __bool__ support in RawQueryset
-+-
   Reporter:  Adnan  |  Owner:  nobody
  Umer   |
   Type:  New| Status:  new
  feature|
  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  |
-+-
 `__len__` & `__bool__` are not implemented because of not having internal
 results caching in RawQueryset.
 https://code.djangoproject.com/ticket/28600 adds support for that.

 `__len__` & `__bool__` supports need to be added for `RawQueryset`

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

Re: [Django] #27391: Support unittest.TestCase.debug() method

[Django]

#27391: Support unittest.TestCase.debug() method
-+-
 Reporter:  Pavel Savchenko  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  unittest | Triage Stage:  Accepted
  SimpleTestCase debug   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

 * needs_docs:  0 => 1
 * version:  1.10 => 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/067.7e6763ffe8329710d9061052d57f1abc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * cc: Carlton Gibson (added)


Comment:

 Replying to [comment:10 Adnan Umer]:
 > Replying to [comment:9 Simon Charette]:
 > > Unless `__bool__` and `__len__` support is required for
 `prefetch_related` to work they should be added/tracked in another
 PR/ticket.
 >
 > Got that. Moving that to separate PR.

 Did that happen? (I
 [https://github.com/django/django/pulls?utf8=✓=is%3Apr+author%3Auadnan
 can't see another PR by Adnan])

 I ask because the warning in
 
[https://github.com/django/django/blob/7a22d9f75125e3cfbea0979a876efe4634f6fe05/docs/topics/db/sql.txt#L88-L97
 docs/db/sql.txt] about this will also need updating:

 `__bool__()` and `__len__()` are not defined in `RawQuerySet`, and
 thus all ``RawQuerySet`` instances are considered `True`. The reason
 these methods are not implemented in `RawQuerySet` is that
 implementing
 them without internal caching would be a performance drawback and
 adding
 such caching would be backward incompatible.

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

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_docs:  0 => 1


Comment:

 Patch is looking good. Just needs some adjustments to the documentation
 changes.

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

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