Re: [Django] #35174: asend() crashes when all receivers are asynchronous functions.

[Django]

#35174: asend() crashes when all receivers are asynchronous functions.
-+
 Reporter:  Vašek Dohnal |Owner:  Vašek Dohnal
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * owner:  nobody => Vašek Dohnal
 * status:  new => assigned

Comment:

 Great, thanks!
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d87b7f870-a317cd83-51f2-4c0f-9a20-bfdc50554377-00%40eu-central-1.amazonses.com.

Re: [Django] #35174: asend() crashes when all receivers are asynchronous functions.

[Django]

#35174: asend() crashes when all receivers are asynchronous functions.
-+
 Reporter:  Vašek Dohnal |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Comment (by Vašek Dohnal):

 I'll do my best and prepare a 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d87b57880-c947a58a-63d7-45b2-9334-b0d95e7fb3e7-00%40eu-central-1.amazonses.com.

Re: [Django] #35073: models.SET's callable is called when there are no objects to update.

[Django]

#35073: models.SET's callable is called when there are no objects to update.
-+-
 Reporter:  Fabio Sangiovanni|Owner:  O'ktamjon
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1

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

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

Re: [Django] #35173: DisallowedModelAdminLookup raised when filtering with __isnull on a ForeignKey not listed in list_filters

[Django]

#35173: DisallowedModelAdminLookup raised when filtering with __isnull on a
ForeignKey not listed in list_filters
-+
 Reporter:  Stian Jensen |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * cc: Sarah Boyce (added)
 * type:  Uncategorized => Bug
 * component:  Uncategorized => contrib.admin
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted

Comment:

 Thanks for the report.

 Regression in f80669d2f5a5f1db9e9b73ca893fefba34f955e7 (Django 5.0.1)
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d87219684-d508f291-76d9-4bb9-96ac-90de2ead888d-00%40eu-central-1.amazonses.com.

Re: [Django] #35174: asend() crashes when all receivers are asynchronous functions. (was: The newly introduced Signal.asend returns TypeError: unhashable type: 'list' if all receivers are asynchronous

[Django]

#35174: asend() crashes when all receivers are asynchronous functions.
-+
 Reporter:  Vašek Dohnal |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * cc: Jon Janzen, Carlton Gibson (added)
 * summary:
 The newly introduced Signal.asend returns TypeError: unhashable type:
 'list' if all receivers are asynchronous functions
 => asend() crashes when all receivers are asynchronous functions.
 * component:  Uncategorized => Core (Other)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted

Comment:

 Great catch! Thanks for the report. Would you like to prepare a patch and
 submit it via GitHub PR? (a regression test is required)

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

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d870b3364-e0960363-2cb2-41c9-a800-fa505ee32f9f-00%40eu-central-1.amazonses.com.

Re: [Django] #28646: Migration calls "CREATE INDEX" when one already exists when 'unique' field attribute is added (PostgreSQL)

[Django]

#28646: Migration calls "CREATE INDEX" when one already exists when 'unique' 
field
attribute is added (PostgreSQL)
-+-
 Reporter:  Hari - 何瑞理|Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  postgresql,migration,index,#djangocph|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d86fc1e5a-358ee85c-1d24-4f2d-902e-b0b125f2b648-00%40eu-central-1.amazonses.com.

Re: [Django] #35167: JSONFIeld get_db_prep_value being called with `Cast` types

[Django]

#35167: JSONFIeld get_db_prep_value being called with `Cast` types
-+-
 Reporter:  Samantha Hughes  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  JSONField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Simon Charette):

 > Any idea if this will make it to a 4.2 patch or will we need to upgrade
 to ~5?

 Assuming someone prepares a patch it should make the cut for 5.1 meant to
 be released in August 2024. It won't be backported to 4.2 or 5.0 at this
 point unfortunately.
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d86d86811-94ef27b6-e565-4ed7-9487-512dcb11ef6a-00%40eu-central-1.amazonses.com.

Re: [Django] #35167: JSONFIeld get_db_prep_value being called with `Cast` types

[Django]

#35167: JSONFIeld get_db_prep_value being called with `Cast` types
-+-
 Reporter:  Samantha Hughes  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  JSONField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * owner:  (none) => nobody
 * component:  Error reporting => Database layer (models, ORM)

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

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d86d5866b-27805ced-0730-4ccf-bd2c-d0f136f8f207-00%40eu-central-1.amazonses.com.

Re: [Django] #24018: Support journal_mode=WAL for sqlite

[Django]

#24018: Support journal_mode=WAL for sqlite
-+-
 Reporter:  Curtis Maloney   |Owner:  Aaron
 |  Linville
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by bcail):

 @Aaron, are you still wanting to work on this? If so, if you fix the tests
 you could update the flags on this issue so it goes back in the list of
 tickets to be reviewed.
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d8577cece-307a4859-67c6-443d-a55d-41b43c5af51d-00%40eu-central-1.amazonses.com.

Re: [Django] #35099: Combining QuerySets with "|" or "&" mutates right-hand side.

[Django]

#35099: Combining QuerySets with "|" or "&" mutates right-hand side.
-+-
 Reporter:  Alan |Owner:  Hisham
 |  Mahmood
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (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
-+-
Comment (by Alan):

 Thank you, Hisham Mahmood and Mariusz, for picking this up.

 Sorry for leaving this hanging. I got overwhelmed on my main job, so
 wasn't able to find a spare hour for this.
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #26001: Make ModelAdmin.search_fields raise data errors on __exact lookups for non-string fields.

[Django]

#26001: Make ModelAdmin.search_fields raise data errors on __exact lookups for 
non-
string fields.
--+
 Reporter:  Tim Graham|Owner:  Saurabh
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.admin |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Saurabh ):

 * owner:  (none) => Saurabh
 * status:  new => assigned

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d84a0d1d8-aff450db-8773-4b61-83a9-81939bc29e41-00%40eu-central-1.amazonses.com.

Re: [Django] #35140: Increase font size in Django debug views (404, 500, etc)

[Django]

#35140: Increase font size in Django debug views (404, 500, etc)
-+-
 Reporter:  Eliana Rosselli  |Owner:  Eliana
 |  Rosselli
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility font   | Triage Stage:  Accepted
  size   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Thibaud Colas):

 Font sizes are defined, for example see
 
[https://github.com/django/django/blob/d79fba7d8e7bbcdf53535a14d57ead5a6863cd8d/django/views/templates/technical_404.html#L11
 technical_404.html line 11].

 A fix for this would either involve removing those definitions, or
 replacing them with more explicit ones, Eli and I haven’t investigated
 yet. As far as browser settings, it will be equally good as long as we
 appropriately use font size units that are relative. So in the case of
 `1.5rem` – the value is fixed relative to the root (`html` element) font
 size, which is where the browser settings would apply (as far as I know,
 it’s not always explicit enough 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/0107018d840f3426-30436e2f-352f-42a0-ad8c-41822c977a26-00%40eu-central-1.amazonses.com.

[Django] #35174: The newly introduced Signal.asend returns TypeError: unhashable type: 'list' if all receivers are asynchronous functions

[Django]

#35174: The newly introduced Signal.asend returns TypeError: unhashable type:
'list' if all receivers are asynchronous functions
-+
   Reporter:  Vašek Dohnal   |  Owner:  nobody
   Type:  Bug| 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  |
-+
 == About this issue

 Django 5 added support for asynchronous signals using the `asend` and
 `asend_robust` methods
 ([https://docs.djangoproject.com/en/5.0/releases/5.0/#signals]). If a
 signal is created with **only asynchronous receivers**, the `asend` (or
 `asend_robust`) function call will crash on this error:


 {{{
 Traceback (most recent call last):
   File "C:\Users\***-py3.11\Lib\site-packages\asgiref\sync.py", line 534,
 in thread_handler
 raise exc_info[1]
   File "C:\Users\***-py3.11\Lib\site-
 packages\django\core\handlers\exception.py", line 42, in inner
 response = await get_response(request)
^^^
   File "C:\Users\***-py3.11\Lib\site-packages\asgiref\sync.py", line 534,
 in thread_handler
 raise exc_info[1]
   File "C:\Users\***-py3.11\Lib\site-
 packages\django\core\handlers\base.py", line 253, in _get_response_async
 response = await wrapped_callback(
^^^
   File "C:\work\contrib\django-asgi-lifespan\signals.py", line 47, in root
 await my_signal.asend_robust(sender=None)
   File "C:\Users\***-py3.11\Lib\site-
 packages\django\dispatch\dispatcher.py", line 393, in asend_robust
 responses, async_responses = await asyncio.gather(
^^^
   File
 "C:\Users\***\AppData\Local\Programs\Python\Python311\Lib\asyncio\tasks.py",
 line 826, in gather
 if arg not in arg_to_fut:
^
 TypeError: unhashable type: 'list'
 }}}


 == Sample project demonstrating the error

 Create file `signals.py` with this content:

 {{{#!python
 import asyncio
 import logging

 from django import conf, http, urls
 from django.core.handlers.asgi import ASGIHandler
 from django.dispatch import Signal, receiver

 logging.basicConfig(level=logging.DEBUG)
 conf.settings.configure(
 ALLOWED_HOSTS="*",
 ROOT_URLCONF=__name__,
 LOGGING=None,
 )

 app = ASGIHandler()
 my_signal = Signal()


 @receiver(my_signal)
 async def my_async_receiver(sender, **kwargs):
 logging.info("my_async_receiver::started")
 await asyncio.sleep(1)
 logging.info("my_async_receiver::finished")


 async def root(request):
 logging.info("root::started")
 await my_signal.asend_robust(sender=None)
 logging.info("root::ended")
 return http.JsonResponse({"message": "Hello World"})


 urlpatterns = [urls.path("", root)]
 }}}


 Run this file:


 {{{
 uvicorn signals:app --log-level=DEBUG --reload
 }}}

 Execute the view:

 {{{
 curl -v http://127.0.0.1:8000
 }}}

 See the error.


 If we modify the above code and add at least one synchronous receiver,
 everything will work fine.

 {{{#!python
 import asyncio
 import logging
 import time

 from django import conf, http, urls
 from django.core.handlers.asgi import ASGIHandler
 from django.dispatch import Signal, receiver

 logging.basicConfig(level=logging.DEBUG)
 conf.settings.configure(
 ALLOWED_HOSTS="*",
 ROOT_URLCONF=__name__,
 LOGGING=None,
 )

 app = ASGIHandler()
 my_signal = Signal()


 @receiver(my_signal)
 async def my_async_receiver(sender, **kwargs):
 logging.info("my_async_receiver::started")
 await asyncio.sleep(1)
 logging.info("my_async_receiver::finished")


 @receiver(my_signal)
 def my_standard_receiver(sender, **kwargs):
 logging.info("my_standard_receiver::started")
 time.sleep(1)
 logging.info("my_standard_receiver::finished")


 async def root(request):
 logging.info("root::started")
 await my_signal.asend_robust(sender=None)
 logging.info("root::ended")
 return http.JsonResponse({"message": "Hello World"})


 urlpatterns = [urls.path("", root)]
 }}}

 Output of uvicorn in this case:

 {{{
 INFO: Started server process [80144]
 INFO: Waiting for application startup.
 INFO: ASGI 'lifespan' protocol appears unsupported.
 INFO: Application startup complete.
 INFO:root:root::started
 INFO:root:my_async_receiver::started
 INFO:root:my_standard_receiver::started
 INFO:root:my_standard_receiver::finished
 INFO:root:my_async_receiver::finished
 INFO:root:root::ended
 INFO: 127.0.0.1:60295 - "GET / HTTP/1.1" 200 OK
 }}}

 == Proposed solution

 In my opinion, the error is 

Re: [Django] #28646: Migration calls "CREATE INDEX" when one already exists when 'unique' field attribute is added (PostgreSQL)

[Django]

#28646: Migration calls "CREATE INDEX" when one already exists when 'unique' 
field
attribute is added (PostgreSQL)
-+-
 Reporter:  Hari - 何瑞理|Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  postgresql,migration,index,#djangocph|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bcail):

 * 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/0107018d83b13e83-ca5f1307-2e39-40f5-b6ab-225e3c66357b-00%40eu-central-1.amazonses.com.

Re: [Django] #35099: Combining QuerySets with "|" or "&" mutates right-hand side.

[Django]

#35099: Combining QuerySets with "|" or "&" mutates right-hand side.
-+-
 Reporter:  Alan |Owner:  Hisham
 |  Mahmood
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (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:"d79fba7d8e7bbcdf53535a14d57ead5a6863cd8d" d79fba7d]:
 {{{#!CommitTicketReference repository=""
 revision="d79fba7d8e7bbcdf53535a14d57ead5a6863cd8d"
 Fixed #35099 -- Prevented mutating queryset when combining with & and |
 operators.

 Thanks Alan for the report.

 Co-authored-by: Mariusz Felisiak 
 }}}
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d83810b07-021ad042-f825-429e-bf1a-d965887b4691-00%40eu-central-1.amazonses.com.

[Django] #35173: DisallowedModelAdminLookup raised when filtering with __isnull on a ForeignKey not listed in list_filters

[Django]

#35173: DisallowedModelAdminLookup raised when filtering with __isnull on a
ForeignKey not listed in list_filters
-+
   Reporter:  Stian Jensen   |  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  |
-+
 A regression in Django 5.0 was previously reported and fixed, relating to
 filtering foreign keys in django-admin in the URL, when not manually
 declared in list_filters:
 https://code.djangoproject.com/ticket/35087

 There is at least one more issue I'm still having, that is still
 problematic in Django 5.0.2:

 Filtering by whether or not a foreign key value is set also used to work
 for any foreign key on the model.
 `/admin/core/invoice/?client__isnull=True`

 In Django 5.0.2 this provides an error similar to the error reported in
 35087.
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d831ec465-dd5ef578-1288-4498-a3f6-bd9a6e7d8982-00%40eu-central-1.amazonses.com.

Re: [Django] #35099: Combining QuerySets with "|" or "&" mutates right-hand side.

[Django]

#35099: Combining QuerySets with "|" or "&" mutates right-hand side.
-+-
 Reporter:  Alan |Owner:  Hisham
 |  Mahmood
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Alan => Hisham Mahmood
 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin

Comment:

 [https://github.com/django/django/pull/17829 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d83045ed8-de59cac1-c6b5-4022-bff2-b878e5c4eb38-00%40eu-central-1.amazonses.com.

Re: [Django] #30686: Improve utils.text.Truncator to use a full HTML parser.

[Django]

#30686: Improve utils.text.Truncator  to use a full HTML parser.
-+-
 Reporter:  Thomas Hooper|Owner:  David
 |  Smith
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  dev
 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:"6ee37ada3241ed263d8d1c2901b030d964cbd161" 6ee37ad]:
 {{{#!CommitTicketReference repository=""
 revision="6ee37ada3241ed263d8d1c2901b030d964cbd161"
 Fixed #30686 -- Used Python HTMLParser in utils.text.Truncator.
 }}}
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"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/0107018d8300f101-d347f871-c627-4025-a4bd-53ab2c31456d-00%40eu-central-1.amazonses.com.

Re: [Django] #30686: Improve utils.text.Truncator to use a full HTML parser.

[Django]

#30686: Improve utils.text.Truncator  to use a full HTML parser.
-+-
 Reporter:  Thomas Hooper|Owner:  David
 |  Smith
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  dev
 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 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/0107018d82c00d76-a9ee910f-552f-44a9-920a-cc7fa3ef69e2-00%40eu-central-1.amazonses.com.