Re: [Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  slice F  | 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 GitHub ):

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


Comment:

 In [changeset:"94b6f101f7dc363a8e71593570b17527dbb9f77f" 94b6f10]:
 {{{
 #!CommitTicketReference repository=""
 revision="94b6f101f7dc363a8e71593570b17527dbb9f77f"
 Fixed #29049 -- Added slicing notation to F expressions.

 Co-authored-by: Priyansh Saxena 
 Co-authored-by: Niclas Olofsson 
 Co-authored-by: David Smith 
 Co-authored-by: Mariusz Felisiak 
 Co-authored-by: Abhinav Yadav 
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb99c4529-4d87303d-69bc-43c2-960a-be293c2df0b2-00%40eu-central-1.amazonses.com.

Re: [Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
 Reporter:  Matthew Pava |Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  slice F  | 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 Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb996086a-65dd9a4b-1b3a-486c-8ff1-386436cc0099-00%40eu-central-1.amazonses.com.

Re: [Django] #34670: Django Admin light theme flickers on dark system

[Django]

#34670: Django Admin light theme flickers on dark system
-+-
 Reporter:  Thomas Feldmann  |Owner:  Nicolas
 Type:   |  Lupien
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 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:  1
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"561e16d6a7f07d8cadbdb6c72c68934dcd087d18" 561e16d]:
 {{{
 #!CommitTicketReference repository=""
 revision="561e16d6a7f07d8cadbdb6c72c68934dcd087d18"
 Fixed #34670 -- Improved loading of theme in admin.

 Thanks Sarah Abderemane for the review.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb988cf7e-efc002c7-4c03-4ea3-995d-1a0003a6f700-00%40eu-central-1.amazonses.com.

Re: [Django] #34670: Django Admin light theme flickers on dark system

[Django]

#34670: Django Admin light theme flickers on dark system
-+-
 Reporter:  Thomas Feldmann  |Owner:  Nicolas
 Type:   |  Lupien
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 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:  1
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb9872447-00fde358-2c69-4dd2-be76-d851ecef31b5-00%40eu-central-1.amazonses.com.

Re: [Django] #35070: Default form output in docs is shown as as_table() instead of as_div()

[Django]

#35070: Default form output in docs is shown as as_table() instead of as_div()
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Zowie Beha):

 Replying to [comment:4 Mariusz Felisiak]:
 > These docs are correct for Django 4.2.
 >
 > `` became the default form rendering style when outputting a form
 in Django 5.0, check out
 [https://docs.djangoproject.com/en/dev/releases/4.1/#form-rendering-
 accessibility release notes].

 Oops! Thank you, I didn't notice the link was for 4.2 instead of 5.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb856e252-c790f430-4c0e-4af2-b7bf-9e9dbe273478-00%40eu-central-1.amazonses.com.

Re: [Django] #35070: Default form output in docs is shown as as_table() instead of as_div()

[Django]

#35070: Default form output in docs is shown as as_table() instead of as_div()
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * version:  5.0 => 4.2
 * resolution:   => invalid


Comment:

 These docs are correct for Django 4.2.

 `` became the default form rendering style when outputting a form in
 Django 5.0, check out [https://docs.djangoproject.com/en/dev/releases/4.1
 /#form-rendering-accessibility release notes].

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb736f773-075fe5c0-4b35-424a-babe-602523606d9f-00%40eu-central-1.amazonses.com.

Re: [Django] #35069: Typo in Form.label_suffix example in docs. (was: Form docs label_suffix example has incorrect output)

[Django]

#35069: Typo in Form.label_suffix example in docs.
--+
 Reporter:  Zowie Beha|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  form, documentation   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Good catch, it looks like a typo in the
 9ac97e7eb5a74f813012715c7598c8608e78e178:
 {{{#!diff
 diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt
 index 7bec9b120b..28cd452c4e 100644
 --- a/docs/ref/forms/api.txt
 +++ b/docs/ref/forms/api.txt
 @@ -909,7 +909,7 @@ It's possible to customize that character, or omit it
 entirely, using the
  Cc myself
  >>> f = ContactForm(auto_id="id_for_%s", label_suffix=" ->")
  >>> print(f)
 -Subject:
 +Subject ->
  Message ->
  Sender ->
  Cc myself ->

 }}}

 Would you like to prepare a patch (via GitHub PR)?

 For the future, tickets are not necessary to fix typos in docs.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb727e46c-d26f986f-a88c-4f7a-93f6-b0e82bc9990d-00%40eu-central-1.amazonses.com.

Re: [Django] #35072: Model docs Field.choices inconsistency between reference and topic guide

[Django]

#35072: Model docs Field.choices inconsistency between reference and topic guide
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:
  model, field   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * cc: Zowie Beha (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb709ea77-d276a1db-5ae6-459d-a26c-7c5a67d62225-00%40eu-central-1.amazonses.com.

Re: [Django] #35072: Model docs Field.choices inconsistency between reference and topic guide

[Django]

#35072: Model docs Field.choices inconsistency between reference and topic guide
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:
  model, field   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Zowie Beha:

Old description:

> https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices
>
> On this reference page, Field.choices is described as:
> "A mapping or iterable in the format described below to use as choices
> for this field."
>
> https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options
>
> Here on the topic guide however, the description is:
> "A sequence of 2-tuples to use as choices for this field."
>
> I think this inconsistency is present because support for mappings as
> choices was introduced in Django 5.0, and the topic page hasn't yet been
> updated to reflect that change. It should also be mentioned in the topic
> guide that a callable is a valid choice value.

New description:

 
https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices

 On this reference page, Field.choices is described as:
 "A mapping or iterable in the format described below to use as choices for
 this field."

 https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options

 Here on the topic guide however, the description is:
 "A sequence of 2-tuples to use as choices for this field."

 I think this inconsistency is present because support for mappings as
 choices was introduced in Django 5.0, and the topic page hasn't yet been
 updated to reflect that change. It should also be mentioned in the topic
 guide that a callable is a valid choices value.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb709488c-39d19776-e7d7-4de6-92ac-6e0bfc638ab7-00%40eu-central-1.amazonses.com.

Re: [Django] #35072: Model docs Field.choices inconsistency between reference and topic guide

[Django]

#35072: Model docs Field.choices inconsistency between reference and topic guide
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:
  model, field   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Zowie Beha:

Old description:

> https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices
>
> On this reference page, Field.choices is described as:
> "A mapping or iterable in the format described below to use as choices
> for this field."
>
> https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options
>
> Here on the topic guide however, the description is:
> "A sequence of 2-tuples to use as choices for this field."
>
> I think this inconsistency is present because support for mappings as
> choices was introduced in Django 5.0, and the topic page hasn't yet been
> updated to reflect that change. It should also be mentioned that a
> callable is a valid choice value.

New description:

 
https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices

 On this reference page, Field.choices is described as:
 "A mapping or iterable in the format described below to use as choices for
 this field."

 https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options

 Here on the topic guide however, the description is:
 "A sequence of 2-tuples to use as choices for this field."

 I think this inconsistency is present because support for mappings as
 choices was introduced in Django 5.0, and the topic page hasn't yet been
 updated to reflect that change. It should also be mentioned in the topic
 guide that a callable is a valid choice value.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb70864ae-7bcdd1af-39bf-463c-9504-9d5c6014de87-00%40eu-central-1.amazonses.com.

Re: [Django] #35072: Model docs Field.choices inconsistency between reference and topic guide

[Django]

#35072: Model docs Field.choices inconsistency between reference and topic guide
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:
  model, field   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Zowie Beha:

Old description:

> https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices
>
> On this reference page, Field.choices is described as:
> "A mapping or iterable in the format described below to use as choices
> for this field."
>
> https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options
>
> Here on the topic guide however, the description is:
> "A sequence of 2-tuples to use as choices for this field."
>
> I think this inconsistency is present because support for mappings as
> choices was introduced in Django 5.0, and the topic page hasn't yet been
> updated to reflect that change.

New description:

 
https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices

 On this reference page, Field.choices is described as:
 "A mapping or iterable in the format described below to use as choices for
 this field."

 https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options

 Here on the topic guide however, the description is:
 "A sequence of 2-tuples to use as choices for this field."

 I think this inconsistency is present because support for mappings as
 choices was introduced in Django 5.0, and the topic page hasn't yet been
 updated to reflect that change. It should also be mentioned that a
 callable is a valid choice value.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb7076bc9-84b5d9fc-08d4-46f3-b971-2cd153c654ba-00%40eu-central-1.amazonses.com.

[Django] #35072: Model docs Field.choices inconsistency between reference and topic guide

[Django]

#35072: Model docs Field.choices inconsistency between reference and topic guide
-+-
   Reporter:  Zowie  |  Owner:  nobody
  Beha   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  5.0
  Documentation  |   Keywords:  documentation,
   Severity:  Normal |  model, field
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 
https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.choices

 On this reference page, Field.choices is described as:
 "A mapping or iterable in the format described below to use as choices for
 this field."

 https://docs.djangoproject.com/en/5.0/topics/db/models/#field-options

 Here on the topic guide however, the description is:
 "A sequence of 2-tuples to use as choices for this field."

 I think this inconsistency is present because support for mappings as
 choices was introduced in Django 5.0, and the topic page hasn't yet been
 updated to reflect that change.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb7059f6e-9906c5f0-9d27-48df-b2c2-8fc5f4700eb8-00%40eu-central-1.amazonses.com.

[Django] #35071: Resolve lazy translation objects inside dictionaries when saving JSONFields

[Django]

#35071: Resolve lazy translation objects inside dictionaries when saving 
JSONFields
-+-
   Reporter:  Jacob  |  Owner:  nobody
  Walls  |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  4.2
  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  |
-+-
 I have a model `Notification` like this:

 {{{
 class Notification(models.Model):
 message = models.TextField(null=True)
 context = models.JSONField(null=True)
 }}}

 Here is the lazy object...
 {{{
 >>> from django.utils.translation import gettext_lazy as _
 >>> lazy = _("lazy")
 }}}

 ... that I can use in a TextField ...

 {{{
 >>> models.Notification(message=lazy).save()
 >>>
 }}}

 ... but not for the JSONField without string-ifying it myself. Suggesting
 an implementation that resolves these in one of the methods that prepares
 values for database insertion. Tested with psycopg2 2.9.9.
 {{{
 >>> models.Notification(context={'lazy': lazy}).save()
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/base.py", line 814, in save
 self.save_base(
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/base.py", line 877, in save_base
 updated = self._save_table(
   ^
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/base.py", line 990, in _save_table
 updated = self._do_update(
   
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/base.py", line 1054, in _do_update
 return filtered._update(values) > 0

   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/query.py", line 1231, in _update
 return query.get_compiler(self.db).execute_sql(CURSOR)
^^^
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/sql/compiler.py", line 1982, in execute_sql
 cursor = super().execute_sql(result_type)
  
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/models/sql/compiler.py", line 1560, in execute_sql
 cursor.execute(sql, params)
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/backends/utils.py", line 102, in execute
 return super().execute(sql, params)

   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/backends/utils.py", line 67, in execute
 return self._execute_with_wrappers(

   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
 return executor(sql, params, many, context)

   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/django/db/backends/utils.py", line 89, in _execute
 return self.cursor.execute(sql, params)

   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/psycopg2/_json.py", line 78, in getquoted
 s = self.dumps(self.adapted)
 
   File "/Users/jwalls/venv311/lib/python3.11/site-
 packages/psycopg2/_json.py", line 72, in dumps
 return self._dumps(obj)

   File
 
"/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/__init__.py",
 line 231, in dumps
 return _default_encoder.encode(obj)

   File
 
"/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/encoder.py",
 line 200, in encode
 chunks = self.iterencode(o, _one_shot=True)
  ^^
   File
 
"/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/encoder.py",
 line 258, in iterencode
 return _iterencode(o, 0)
^
   File
 
"/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/encoder.py",
 line 180, in default
 raise TypeError(f'Object of type {o.__class__.__name__} '
 TypeError: Object of type __proxy__ is not JSON serializable
 }}}

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

-

Re: [Django] #35069: Form docs label_suffix example has incorrect output (was: Form documentation example has incorrect output)

[Django]

#35069: Form docs label_suffix example has incorrect output
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6ef7506-b654977f-a2e8-41c1-8ab3-46b25c5e9e34-00%40eu-central-1.amazonses.com.

Re: [Django] #35069: Form documentation example has incorrect output

[Django]

#35069: Form documentation example has incorrect output
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * cc: Zowie Beha (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6ee8e58-a29578b4-f65f-443f-ac55-a215c293bf8f-00%40eu-central-1.amazonses.com.

Re: [Django] #35070: Default form output in docs is shown as as_table() instead of as_div()

[Django]

#35070: Default form output in docs is shown as as_table() instead of as_div()
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * cc: Zowie Beha (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6ee5725-1c7f6f74-481f-4974-aef6-71bb90777e01-00%40eu-central-1.amazonses.com.

Re: [Django] #35070: Default form output in docs is shown as as_table() instead of as_div()

[Django]

#35070: Default form output in docs is shown as as_table() instead of as_div()
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * type:  Bug => Cleanup/optimization


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6df3fe1-cafb3a00-00f2-445d-be54-f2599ced9318-00%40eu-central-1.amazonses.com.

Re: [Django] #35070: Default form output in docs is shown as as_table() instead of as_div() (was: Default form output is shown as as_table() instead of as_div())

[Django]

#35070: Default form output in docs is shown as as_table() instead of as_div()
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6dec5b1-7dcd8f41-c3f6-4c68-a2f7-1f15cf69b7d2-00%40eu-central-1.amazonses.com.

[Django] #35070: Default form output is shown as as_table() instead of as_div()

[Django]

#35070: Default form output is shown as as_table() instead of as_div()
-+-
   Reporter:  Zowie  |  Owner:  nobody
  Beha   |
   Type:  Bug| Status:  new
  Component: |Version:  5.0
  Documentation  |
   Severity:  Normal |   Keywords:  form, documentation
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 https://docs.djangoproject.com/en/4.2/ref/forms/api/#outputting-forms-as-
 html

 "This default output is a two-column HTML table, with a  for each
 field."

 "...  output is the default output style when you print a form
 ..."

 The examples in this section show that if you print a form, it will render
 as an html table.
 However, if I try the examples locally, the form is rendered as a series
 of div elements.
 This leads me to think that the documentation doesn't reflect this new
 default.
 I'm not sure when this default was introduced, but it might be ~Django
 version 4.1, as that is when as_div() was 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6dccb40-baaec279-53b0-4ae1-88a1-eae1d67c42c4-00%40eu-central-1.amazonses.com.

Re: [Django] #35069: Form documentation example has incorrect output

[Django]

#35069: Form documentation example has incorrect output
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * component:  Uncategorized => Documentation


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6d46389-20157ac2-9cda-4fda-9db0-1deb64e7a053-00%40eu-central-1.amazonses.com.

Re: [Django] #35069: Form documentation example has incorrect output

[Django]

#35069: Form documentation example has incorrect output
-+-
 Reporter:  Zowie Beha   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Uncategorized|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  form, documentation  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Zowie Beha):

 * Attachment "9wgvVRd.png" added.

 The subject label has the suffix ':', while label_suffix sets it 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6d1dfd6-e5fcea39-df47-4345-8d7b-5913f195a106-00%40eu-central-1.amazonses.com.

[Django] #35069: Form documentation example has incorrect output

[Django]

#35069: Form documentation example has incorrect output
-+-
   Reporter:  Zowie  |  Owner:  nobody
  Beha   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  5.0
  Uncategorized  |
   Severity:  Normal |   Keywords:  form, documentation
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 
https://docs.djangoproject.com/en/5.0/ref/forms/api/#django.forms.Form.label_suffix
 https://i.imgur.com/9wgvVRd.png

 Hi everyone,

 in this example, a form is created with the label_suffix set to " ->".
 When this form is printed, the output shows that the Subject label does
 not reflect this change. This leads me to think this line may be a
 mistake.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb6d0d408-3409c801-e589-4e22-ace3-ed28ab96ad98-00%40eu-central-1.amazonses.com.

Re: [Django] #35068: decimal as Float in settings

[Django]

#35068: decimal as Float in settings
---+--
 Reporter:  Петр Eлагин|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  5.0
 Severity:  Normal |   Resolution:  invalid
 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 Mariusz Felisiak):

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


Comment:

 Please stop to create tickets without any details and follow our
 [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/#reporting-bugs bug reporting guidelines] next time.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb5aeb899-58c3c1e8-c753-4c09-a897-efeaec6c4620-00%40eu-central-1.amazonses.com.

[Django] #35068: decimal as Float in settings

[Django]

#35068: decimal as Float in settings
-+
   Reporter:  Петр Eлагин|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  5.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  |
-+
 from psycopg.types.numeric import FloatLoader

 site-packages/django/db/backends/postgresql/psycopg_any.py

 line 63:

 ctx.register_loader("numeric", FloatLoader)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb536d7ff-bbdbb811-afe8-450f-89d4-5547c32b85ea-00%40eu-central-1.amazonses.com.

Re: [Django] #32114: Workaround for subtest issue with parallel test runner

[Django]

#32114: Workaround for subtest issue with parallel test runner
-+-
 Reporter:  Jordan Ephron|Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Test subtest | Triage Stage:  Accepted
  parallel   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Wobrock):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb4d213ab-fb6f41cc-5a5b-473a-8691-4ae0b3b992f0-00%40eu-central-1.amazonses.com.

Re: [Django] #35033: EmailMessage repeats header if provided via the headers kwargs

[Django]

#35033: EmailMessage repeats header if provided via the headers kwargs
+-
 Reporter:  Aalekh Patel|Owner:  Salvo Polizzi
 Type:  Bug |   Status:  assigned
Component:  Core (Mail) |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  email, headers  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Salvo Polizzi):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb4cd2a65-e1e52b8a-dc1c-4b7a-b6b3-7c051660d623-00%40eu-central-1.amazonses.com.

Re: [Django] #31723: Lag() with DecimalField crashes on SQLite.

[Django]

#31723: Lag() with DecimalField crashes on SQLite.
-+-
 Reporter:  qwango   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Lag  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"e16d0c176e9b89628cdec5e58c418378c4a2436a" e16d0c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="e16d0c176e9b89628cdec5e58c418378c4a2436a"
 Fixed #35064 -- Fixed Window(order_by) crash with DecimalFields on SQLite.

 This avoids cast of Window(order_by) for DecimalFields on SQLite.

 This was achieved by piggy-backing ExpressionList which already
 implements a specialized as_sqlite() method to override the inherited
 behaviour of Func through SQLiteNumericMixin.

 Refs #31723.

 Thanks Quoates for the report.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb4cc3c2c-2fdf872d-ba6b-4afc-8ad6-71baca3b0bd7-00%40eu-central-1.amazonses.com.

Re: [Django] #35064: Window.order_by decimal field is broken on SQLite

[Django]

#35064: Window.order_by decimal field is broken on SQLite
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"90d365d869924d503565eb1ccdc24077d60faf0c" 90d365d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="90d365d869924d503565eb1ccdc24077d60faf0c"
 Refs #35064 -- Made OrderableAggMixin avoid creating empty OrderByList.

 This paves the way for making OrderByList a simple shim over
 ExpressionList which requires at least a single item to be provided.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb4cc3bba-c3e49a3c-4c32-4f05-8606-937cf591c74e-00%40eu-central-1.amazonses.com.

Re: [Django] #35064: Window.order_by decimal field is broken on SQLite

[Django]

#35064: Window.order_by decimal field is broken on SQLite
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"e16d0c176e9b89628cdec5e58c418378c4a2436a" e16d0c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="e16d0c176e9b89628cdec5e58c418378c4a2436a"
 Fixed #35064 -- Fixed Window(order_by) crash with DecimalFields on SQLite.

 This avoids cast of Window(order_by) for DecimalFields on SQLite.

 This was achieved by piggy-backing ExpressionList which already
 implements a specialized as_sqlite() method to override the inherited
 behaviour of Func through SQLiteNumericMixin.

 Refs #31723.

 Thanks Quoates for the report.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cb4cc3be4-6114223d-4e8b-49eb-9a1b-385775f69a96-00%40eu-central-1.amazonses.com.