Re: [Django] #29159: ModelChoiceIterator triggers duplicate queries when choices are cast to list

[Django]

#29159: ModelChoiceIterator triggers duplicate queries when choices are cast to
list
-+-
 Reporter:  François Freitag |Owner:  François
 |  Freitag
 Type:  Uncategorized|   Status:  assigned
Component:  Forms|  Version:  1.8
 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 François Freitag):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9726 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/073.c52fd096b19e8933d0a2f3ed7805d0c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29158: ModelChoiceField crashes when checking choices' length

[Django]

#29158: ModelChoiceField crashes when checking choices' length
-+-
 Reporter:  François Freitag |Owner:  François
 |  Freitag
 Type:  Uncategorized|   Status:  assigned
Component:  Forms|  Version:  1.8
 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 François Freitag):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9725 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/073.84c4196b2e3b282a80aa319a236d5547%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29159: ModelChoiceIterator triggers duplicate queries when choices are cast to list

[Django]

#29159: ModelChoiceIterator triggers duplicate queries when choices are cast to
list
-+-
   Reporter:  François   |  Owner:  François Freitag
  Freitag|
   Type: | Status:  assigned
  Uncategorized  |
  Component:  Forms  |Version:  1.8
   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 there are no `prefetch_related()` on `ModelChoiceIterator`'s
 queryset, it attempts to use the `iterator()` method to avoid loading all
 choices in memory.
 ([https://docs.djangoproject.com/en/2.0/ref/models/querysets/#prefetch-
 related because iterator() and prefetch_related() don't make sense
 together.])

 That results in a duplicate query if the choices have been evaluated
 before, because calling `iterator()` will clone the `QuerySet`, resetting
 its result cache in the process.

 {{{
 class TestModelChoiceField(TestCase):
 def test_queryset_result_cache_is_reused(self):
 choice = ChoiceOptionModel.objects.create(name="choice 1")
 f = ModelChoiceField(ChoiceOptionModel.objects.all())
 with self.assertNumQueries(1):
 self.assertEqual(
 # list calls both __len__ and __iter__
 list(f.choices),
 [('', '-'), (choice.pk, str(choice))],
 )
 }}}


 Fails with:
 {{{
 FAIL: test_queryset_result_cache_is_reused
 (forms_tests.test_tmp.TestModelChoiceField)
 --
 Traceback (most recent call last):
   File "django/tests/forms_tests/test_tmp.py", line 19, in
 test_queryset_result_cache_is_reused
 [('', '-'), (choice.pk, str(choice))],
   File "django/django/test/testcases.py", line 80, in __exit__
 '%d. %s' % (i, query['sql']) for i, query in
 enumerate(self.captured_queries, start=1)
 AssertionError: 2 != 1 : 2 queries executed, 1 expected
 Captured queries were:
 1. SELECT "forms_tests_choiceoptionmodel"."id",
 "forms_tests_choiceoptionmodel"."name" FROM
 "forms_tests_choiceoptionmodel" ORDER BY
 "forms_tests_choiceoptionmodel"."name" ASC
 2. SELECT "forms_tests_choiceoptionmodel"."id",
 "forms_tests_choiceoptionmodel"."name" FROM
 "forms_tests_choiceoptionmodel" ORDER BY
 "forms_tests_choiceoption$odel"."name" ASC
 }}}

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

[Django] #29158: ModelChoiceField crashes when checking choices' length

[Django]

#29158: ModelChoiceField crashes when checking choices' length
-+-
   Reporter:  François   |  Owner:  François Freitag
  Freitag|
   Type: | Status:  assigned
  Uncategorized  |
  Component:  Forms  |Version:  1.8
   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  |
-+-
 ModelChoiceField must accept Manager as a `.queryset` for backward
 compatibility reasons (see #25683). However, `ModelChoiceIterator` does
 not play nice with Managers:


 {{{
 class TestModelChoiceField(TestCase):
 def test_queryset_manager_has_length(self):
 f = ModelChoiceField(ChoiceOptionModel.objects)
 len(f.choices)
 }}}

 Errors with:

 {{{
 ==
 ERROR: test_queryset_manager_has_length
 (forms_tests.test_tmp.TestModelChoiceField)
 --
 Traceback (most recent call last):
   File "django/tests/forms_tests/test_tmp.py", line 10, in
 test_queryset_manager_has_length
 len(f.choices)
   File "django/django/forms/models.py", line 1141, in __len__
 return len(self.queryset) + (1 if self.field.empty_label is not None
 else 0)
 TypeError: object of type 'Manager' has no len()
 }}}

 

 The reason why this `TypeError` was not reported earlier is probably
 because Python swallows `TypeError` silently for `__len__` when `list` is
 called, because generators have no `len`:

 {{{
 Python 3.6.4 (default, Jan  5 2018, 02:35:40)
 [GCC 7.2.1 20171224] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 >>> def gene():
 ... yield 1
 ...
 >>> len(gene())
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: object of type 'generator' has no len()
 >>> list(gene())
 [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/058.3003c1605dda325bb31676e58323b746%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29157: Getting Distinct Values from List in a JSONField

[Django]

#29157: Getting Distinct Values from List in a JSONField
-+
   Reporter:  Hrishikesh Barman  |  Owner:  (none)
   Type:  New feature| Status:  new
  Component:  contrib.postgres   |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 We can access JSONField Data
 
(https://docs.djangoproject.com/en/2.0/ref/contrib/postgres/fields/#django.contrib.postgres.fields.JSONField)
 like this `Dog.objects.filter(data__owner__name='Bob')`

 But for JSONField consisting of a list this does not work.

 {{{
 [{'a':12,'b':33},{'a':44,'b':99}]
 }}}

 Filtering values like this works:

 {{{
 Frame.objects.filter(
 size__contains=[{'a': 12,'b': 33}]
 )
 }}}

 But there is no way to get distinct values from a list in a JSONfield, for
 eg. the following does not work.
 {{{
 Frame.objects.values( 'size__a')
 }}}

 Should there be an implementation of the same?

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

Re: [Django] #29153: Ease customizing the label attrs on a model form field (was: add label attrs to BaseForm)

[Django]

#29153: Ease customizing the label attrs on a model form field
--+--
 Reporter:  ChristophRob  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Forms |  Version:  2.0
 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
--+--
Changes (by Tim Graham):

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


Comment:

 Thanks for the clarifying edits. I guess you're running into the problem
 described on [https://stackoverflow.com/questions/6959178/how-to-set-css-
 class-of-a-label-in-a-django-form-declaration Stack Overflow].

 I'm not sure if the use case is common enough to add a field attribute for
 this. Usually I style labels using CSS3 selectors. If you can get
 consensus on a proposal on the DevelopersMailingList, we can reopen the
 ticket. Generally, the consensus has been that if you need to make much
 customization to form rendering, you should iterate over the fields rather
 than using `{{ form }}`.

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

Re: [Django] #29156: Enhance the model methods added when Meta.order_with_respect_to is used (was: Increase 'order_with_respect_to' features)

[Django]

#29156: Enhance the model methods added when Meta.order_with_respect_to is used
-+-
 Reporter:  César García Tapia   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Tim Graham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 Ideally, a ticket should propose one feature rather than several. I'm not
 sure what complexity might be involved in these issues, but I guess we
 could evaluate a patch.

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

Re: [Django] #29133: call_command() fails if a required option is passed in via **options

[Django]

#29133: call_command() fails if a required option is passed in via **options
-+-
 Reporter:  Alex Tomic   |Owner:  Alex
 Type:   |  Tomic
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  2.0
  commands)  |
 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 Alex Tomic):

 * needs_better_patch:  1 => 0


Comment:

 Thanks for the feedback. I've simplified the test case and supporting
 management command to only test what was not working before, and pushed up
 a new commit.

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

Re: [Django] #28621: Crash in QuerySet.annotate() with OuterRef

[Django]

#28621: Crash in QuerySet.annotate() with OuterRef
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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 Matthew Schinckel):

 The `relabeled_clone` issue is now fixed: I missed that there is also a
 `contains_aggregate` part. I'll have a look at that now.

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

Re: [Django] #29151: Aliasing pgettext_lazy makes it work unexpected

[Django]

#29151: Aliasing pgettext_lazy makes it work unexpected
-+-
 Reporter:  shutterfire  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  2.0
  Internationalization   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  i18n | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 This is a [https://docs.djangoproject.com/en/dev/topics/i18n/translation
 /#standard-translation limitation of xgettext],

 > Because of how xgettext (used by makemessages) works, only functions
 that take a single string argument can be imported as _``:
 > * `gettext()`
 > * `gettext_lazy()`

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

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

Re: [Django] #29155: Using contains lookup with Substr causes modification of second parameter of Substr

[Django]

#29155: Using contains lookup with Substr causes modification of second 
parameter
of Substr
-+-
 Reporter:  norac89  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham):

 * Attachment "29155-test.diff" added.


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

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

Re: [Django] #29155: Using contains lookup with Substr causes modification of second parameter of Substr (was: Using contains field lookup with Substr database function cause modification of second pa

[Django]

#29155: Using contains lookup with Substr causes modification of second 
parameter
of Substr
-+-
 Reporter:  norac89  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (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 Tim Graham):

 * stage:  Unreviewed => Accepted


Old description:

> My model:
>

> {{{
> class User(models.Model):
> field1 = models.Charfield(max_length=120)
> field2 = models.Charfield(max_length=120)
> }}}
>
> Tried querying the model to get User instances in which field2 start with
> the three first characters of field1.
> Tried the following:
>
> {{{
> User.objects.filter(field2__startswith=Substr(F('field1'), 1, 3))
> }}}
>
> I m getting the following error
>
> {{{
> psycopg2.DataError: invalid input syntax for integer: "1%"
> LINE 1: ...(REPLACE(REPLACE((SUBSTRING("test_user"."field1", '1%',
> 3)),...
> }}}
>
> The second parameter of the substr function seems to be replaced with
> '1%'.

New description:

 My model:


 {{{
 class User(models.Model):
 field1 = models.CharField(max_length=120)
 field2 = models.CharField(max_length=120)
 }}}

 Tried querying the model to get User instances in which field2 start with
 the three first characters of field1.
 Tried the following:

 {{{
 User.objects.filter(field2__startswith=Substr(F('field1'), 1, 3))
 }}}

 I m getting the following error

 {{{
 psycopg2.DataError: invalid input syntax for integer: "1%"
 LINE 1: ...(REPLACE(REPLACE((SUBSTRING("test_user"."field1", '1%', 3)),...
 }}}

 The second parameter of the substr function seems to be replaced with
 '1%'.

--

Comment:

 I'm attaching a test for Django's test suite that fails (on PostgreSQL but
 not SQLite) as of ba37ee9ef882deb8e917f1cae0c586a0a275e731.

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

[Django] #29156: Increase 'order_with_respect_to' features

[Django]

#29156: Increase 'order_with_respect_to' features
-+-
   Reporter:  tapia  |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  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  |
-+-
 With `order_with_respect_to`, we can do something like this:

 {{{
 class Book(models.Model):
 pass

 class Chapter(models.Model):
 book = models.ForeignKey(Book, on_delete=models.CASCADE)

 class Meta:
 order_with_respect_to = 'book'
 }}}

 It would be very nice to add some obvious features to this feature, for
 example:

 * `book.get_chapter_order()` returns the IDs of the chapters. Why not the
 chapter objects itself?

 * Given a chapter, we can get the next and the previous chapters, but we
 can't easily get that chapter's order.

 * It would be very nice to be able to add a chapter directly in a specific
 position, pretty much like python's `insert`. For example:
 `book.insert_chapter(chapter, 3)`

 I know it's a very broad request, but, if you guys like the idea, I'd love
 to take a look if I can add the functions myself (one at a time, to get
 your approval on each of them).

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

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

Re: [Django] #28635: admin's preserved filters don't work if the URL has non-ASCII characters in it

[Django]

#28635: admin's preserved filters don't work if the URL has non-ASCII 
characters in
it
-+-
 Reporter:  Wenli Tsai   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  add_preserved_filters  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ba37ee9ef882deb8e917f1cae0c586a0a275e731" ba37ee9e]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba37ee9ef882deb8e917f1cae0c586a0a275e731"
 Fixed #28635 -- Fixed admin's preserved filters if the URL contains non-
 ASCII characters.
 }}}

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

[Django] #29155: Using contains field lookup with Substr database function cause modification of second parameter of Substr

[Django]

#29155: Using contains field lookup with Substr database function cause
modification of second parameter of Substr
-+-
   Reporter:  norac89|  Owner:  nobody
   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  |
-+-
 My model:


 {{{
 class User(models.Model):
 field1 = models.Charfield(max_length=120)
 field2 = models.Charfield(max_length=120)
 }}}

 Tried querying the model to get User instances in which field2 start with
 the three first characters of field1.
 Tried the following:

 {{{
 User.objects.filter(field2__startswith=Substr(F('field1'), 1, 3))
 }}}

 I m getting the following error

 {{{
 psycopg2.DataError: invalid input syntax for integer: "1%"
 LINE 1: ...(REPLACE(REPLACE((SUBSTRING("test_user"."field1", '1%', 3)),...
 }}}

 The second parameter of the substr function seems to be replaced with
 '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/050.4e6aba39405b6e63587c6bff258327b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27449: Make django.utils.translation.trans_real.get_supported_language_variant public API

[Django]

#27449: Make django.utils.translation.trans_real.get_supported_language_variant
public API
-+-
 Reporter:  Iacopo Spalletti |Owner:  Sebastian
 |  Sangervasi
 Type:  New feature  |   Status:  closed
Component:   |  Version:  1.10
  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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7905815510fb1eae99010ccc0039249d981a121c" 7905815]:
 {{{
 #!CommitTicketReference repository=""
 revision="7905815510fb1eae99010ccc0039249d981a121c"
 Fixed #27449 -- Added
 django.utils.translation.get_supported_language_variant().
 }}}

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

Re: [Django] #29154: Correct examples in pluralize template filter docstring and add tests

[Django]

#29154: Correct  examples in pluralize template filter docstring and add tests
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  2.0
 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:"5033999153f7303a18d94ea2f08ed78545c0f3df" 50339991]:
 {{{
 #!CommitTicketReference repository=""
 revision="5033999153f7303a18d94ea2f08ed78545c0f3df"
 Fixed #29154 -- Corrected examples in pluralize docstring and added 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.f58574270a835733c530a35d28cf1ac1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29154: Correct examples in pluralize template filter docstring and add tests (was: Fix `pluralize` template filter and add some tests)

[Django]

#29154: Correct  examples in pluralize template filter docstring and add tests
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  2.0
 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 Tim Graham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


Comment:

 [https://github.com/django/django/pull/9723 PR] (for future reference,
 this sort of change doesn't require a 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/067.77e6a7678a92054bce1353c91637c8de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28858: Remove 'else' after 'return' or 'raise'

[Django]

#28858: Remove 'else' after 'return' or 'raise'
-+-
 Reporter:  Дилян Палаузов   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Someday/Maybe
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:   => wontfix


Comment:

 The patch has gone stale and the discussion on the PR didn't yield a
 strong consensus. I think the value of trying to enforce some guidelines
 around this style is minimal.

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

[Django] #29154: Fix `pluralize` template filter and add some tests

[Django]

#29154: Fix `pluralize` template filter and add some tests
+
   Reporter:  Hasan Ramezani|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Template system   |Version:  2.0
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Fix `pluralize` template filter and add some 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/052.1e4f9e70fcc686372432a0392fcfe236%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29154: Fix `pluralize` template filter and add some tests

[Django]

#29154: Fix `pluralize` template filter and add some tests
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  2.0
 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 Hasan Ramezani):

 * status:  new => assigned
 * owner:  nobody => Hasan Ramezani


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

Re: [Django] #29153: add label attrs to BaseForm

[Django]

#29153: add label attrs to BaseForm
--+--
 Reporter:  ChristophRob  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  2.0
 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
--+--
Description changed by ChristophRob:

Old description:

> As the label_tag is already set up to give the label class attributes and
> label_suffix, it is quite easy to add this to the BaseForm _html_output()
>
> {{{
> class BoundField:
> def label_tag(self, contents=None, attrs=None, label_suffix=None):
> }}}
>

> {{{
> class BaseForm:
> def _html_output(self, normal_row, error_row, row_ender,
> help_text_html, errors_on_separate_row):
> # ...
> label = bf.label_tag(label) or ''
> }}}

New description:

 Goal:
 Add attributes like "class" to the label tag for inputs.

 Problem:
 Actually the only thing thats stops me from using {{ form }} is the
 incapability to change classes for labels easily. So i have to do it like
 this, for every form and every field:

 {{{
 {{ form.non_field_errors }}
 
 {{ form.subject.errors }}
 Email subject:
 {{ form.subject }}
 

 }}}

 Where it should be changed:
 I would be fine if the label_attrs could be set in BaseForm(), but i think
 the right place would be class Field

 As the label_tag is already set up to give the label class attributes and
 label_suffix, it is quite easy to add this to the BaseForm _html_output()

 {{{
 class BoundField:
 def label_tag(self, contents=None, attrs=None, label_suffix=None):
 }}}


 {{{
 class BaseForm:
 def _html_output(self, normal_row, error_row, row_ender,
 help_text_html, errors_on_separate_row):
 # ...
 label = bf.label_tag(label) or ''
 }}}

--

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

Re: [Django] #29153: add label attrs to BaseForm

[Django]

#29153: add label attrs to BaseForm
--+--
 Reporter:  ChristophRob  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  2.0
 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):

 I don't understand what change you're proposing. Can you provide a patch
 or describe the changes and the use 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/070.448b615ecc2923adc14525dfe74f74f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29153: add label attrs to BaseForm

[Django]

#29153: add label attrs to BaseForm
+
   Reporter:  ChristophRob  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Forms |Version:  2.0
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 As the label_tag is already set up to give the label class attributes and
 label_suffix, it is quite easy to add this to the BaseForm _html_output()

 {{{
 class BoundField:
 def label_tag(self, contents=None, attrs=None, label_suffix=None):
 }}}


 {{{
 class BaseForm:
 def _html_output(self, normal_row, error_row, row_ender,
 help_text_html, errors_on_separate_row):
 # ...
 label = bf.label_tag(label) or ''
 }}}

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

Re: [Django] #29152: Allow more control over ArgumentParser initialization in management commands (was: management commands - more control on ArgumentParser initialization)

[Django]

#29152: Allow more control over ArgumentParser initialization in management
commands
-+-
 Reporter:  Dmitry   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.0
  commands)  |
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Would a hook to provide some additional keyword arguments be sufficient?

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

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

Re: [Django] #28643: Complete the ORM Function Library

[Django]

#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"f82de6bfb1c3dc468f6eb7472b292cc432d00338" f82de6bf]:
 {{{
 #!CommitTicketReference repository=""
 revision="f82de6bfb1c3dc468f6eb7472b292cc432d00338"
 Refs #28643 -- Added Ord, Chr, Left, and Right database functions.
 }}}

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

Re: [Django] #29142: QuerySet crashes when OuterRef is combined with an operator

[Django]

#29142: QuerySet crashes when OuterRef is combined with an operator
-+-
 Reporter:  Michael Barr |Owner:  Matthew
 |  Schinckel
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Tim Graham ):

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


Comment:

 In [changeset:"c412926a2e359afb40738d8177c9f3bef80ee04e" c412926a]:
 {{{
 #!CommitTicketReference repository=""
 revision="c412926a2e359afb40738d8177c9f3bef80ee04e"
 Fixed #29142 -- Fixed crash when OuterRef is used with an operator.
 }}}

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

Re: [Django] #29151: Aliasing pgettext_lazy makes it work unexpected

[Django]

#29151: Aliasing pgettext_lazy makes it work unexpected
-+-
 Reporter:  shutterfire  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  2.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  i18n | 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):

 I'm not sure how aliasing a function could change its behavior. Are you
 sure you haven't made a mistake in your project? Can you provide a failing
 test (tests/i18n/tests.py) or a sample project that demonstrates the
 issue?

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

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

Re: [Django] #29142: QuerySet crashes when OuterRef is combined with an operator (was: OuterRef not being treated as an F Expression)

[Django]

#29142: QuerySet crashes when OuterRef is combined with an operator
-+-
 Reporter:  Michael Barr |Owner:  Matthew
 |  Schinckel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 Tim Graham):

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

Re: [Django] #29147: Postgres JSONField missing to_python

[Django]

#29147: Postgres JSONField missing to_python
-+-
 Reporter:  Javier Buzzi |Owner:  Williams
 |  Mendez
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Can you be more clear about what the unexpected behavior is? (i.e. give a
 failing test for `tests/postgres_tests/test_json.py`)

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

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

Re: [Django] #29147: Postgres JSONField missing to_python

[Django]

#29147: Postgres JSONField missing to_python
-+-
 Reporter:  Javier Buzzi |Owner:  Williams
 |  Mendez
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Javier Buzzi):

 As i understood it was that `to_python()` is the representation of the
 data in python, postgres could save it and do with it what it wants; store
 it binary/urlencode it/ encrypt it for all it wants, but from a python
 perspective that data to me, needs to be represented as a dict/simple type
 (if it is "hello") -- i still don't understand why this is invalid.

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

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

Re: [Django] #28988: Multi-table inheritance breaks GenericRelation querying

[Django]

#28988: Multi-table inheritance breaks GenericRelation querying
--+
 Reporter:  robwa |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  1.11
 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
--+

Comment (by robwa):

 Updated the [https://github.com/django/django/pull/9624 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/063.5afce9327456f8ad944b44240310631f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29142: OuterRef not being treated as an F Expression

[Django]

#29142: OuterRef not being treated as an F Expression
-+-
 Reporter:  Michael Barr |Owner:  Matthew
 |  Schinckel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (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 Matthew Schinckel):

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

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