Groups
Sign in
Groups
Django updates
Conversations
About
Send feedback
Help
Django updates
Contact owners and managers
1–30 of 62391
Mark all as read
Report group
0 selected
Django
6
1:11 PM
[Django] #35399: Reduce the "Case-When" sequence for a bulk_update when the values for a certain field are the same.
#35399: Reduce the "Case-When" sequence for a bulk_update when the values for a certain
unread,
[Django] #35399: Reduce the "Case-When" sequence for a bulk_update when the values for a certain field are the same.
#35399: Reduce the "Case-When" sequence for a bulk_update when the values for a certain
1:11 PM
Django
2
11:55 AM
[Django] #35402: DatabaseFeatures.django_test_skips crashes when it references a class in another test module
#35402: DatabaseFeatures.django_test_skips crashes when it references a class in another test module
unread,
[Django] #35402: DatabaseFeatures.django_test_skips crashes when it references a class in another test module
#35402: DatabaseFeatures.django_test_skips crashes when it references a class in another test module
11:55 AM
Django
2
11:45 AM
[Django] #35401: Document the `conditional_page` decorator
#35401: Document the `conditional_page` decorator --------------------------------------+------------
unread,
[Django] #35401: Document the `conditional_page` decorator
#35401: Document the `conditional_page` decorator --------------------------------------+------------
11:45 AM
Django
11:35 AM
Re: [Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an application
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an
unread,
Re: [Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an application
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an
11:35 AM
Django
8
6:27 AM
[Django] #35365: Add RFC 3824 Auto-Submitted header to emails by default
#35365: Add RFC 3824 Auto-Submitted header to emails by default ---------------------------------+---
unread,
[Django] #35365: Add RFC 3824 Auto-Submitted header to emails by default
#35365: Add RFC 3824 Auto-Submitted header to emails by default ---------------------------------+---
6:27 AM
Django
15
5:47 AM
[Django] #35137: Collapsible error container elements do not indicate that they are interactive
#35137: Collapsible error container elements do not indicate that they are interactive --------------
unread,
[Django] #35137: Collapsible error container elements do not indicate that they are interactive
#35137: Collapsible error container elements do not indicate that they are interactive --------------
5:47 AM
Django
8
4:53 AM
Re: [Django] #35395: slice filter crashes on an empty dict with Python 3.12
#35395: slice filter crashes on an empty dict with Python 3.12 -------------------------------------+
unread,
Re: [Django] #35395: slice filter crashes on an empty dict with Python 3.12
#35395: slice filter crashes on an empty dict with Python 3.12 -------------------------------------+
4:53 AM
Django
8
4:24 AM
[Django] #35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used
#35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used -----------------------------
unread,
[Django] #35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used
#35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used -----------------------------
4:24 AM
Django
18
4:13 AM
Re: [Django] #35382: Remove unused CSS style `.inline-related fieldset.module h3`
#35382: Remove unused CSS style `.inline-related fieldset.module h3` --------------------------------
unread,
Re: [Django] #35382: Remove unused CSS style `.inline-related fieldset.module h3`
#35382: Remove unused CSS style `.inline-related fieldset.module h3` --------------------------------
4:13 AM
Django
Apr 23
Re: [Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an application (was: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an application)
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an
unread,
Re: [Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an application (was: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an application)
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running multiple instances of an
Apr 23
Django
Apr 23
[Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an application
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an
unread,
[Django] #35400: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an application
#35400: SECRET_KEY_FALLBACKS documentation can be misleading when running a multiple instances of an
Apr 23
Django
8
Apr 23
[Django] #35397: override_settings for STORAGES loses OPTIONS
#35397: override_settings for STORAGES loses OPTIONS -------------------------------------+----------
unread,
[Django] #35397: override_settings for STORAGES loses OPTIONS
#35397: override_settings for STORAGES loses OPTIONS -------------------------------------+----------
Apr 23
Django
9
Apr 23
[Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().
#35356: Issue with OneToOneField and recursive relationships in select_related() and only(). --------
unread,
[Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().
#35356: Issue with OneToOneField and recursive relationships in select_related() and only(). --------
Apr 23
Django
6
Apr 23
Re: [Django] #34612: QuerySet.only() doesn't work with select_related() on a reverse OneToOneField relation.
#34612: QuerySet.only() doesn't work with select_related() on a reverse OneToOneField relation. -
unread,
Re: [Django] #34612: QuerySet.only() doesn't work with select_related() on a reverse OneToOneField relation.
#34612: QuerySet.only() doesn't work with select_related() on a reverse OneToOneField relation. -
Apr 23
Django
3
Apr 23
[Django] #35396: QuerySet filters incorrectly pushed to the inner query when applied after a window function filter
#35396: QuerySet filters incorrectly pushed to the inner query when applied after a window function
unread,
[Django] #35396: QuerySet filters incorrectly pushed to the inner query when applied after a window function filter
#35396: QuerySet filters incorrectly pushed to the inner query when applied after a window function
Apr 23
Django
5
Apr 23
[Django] #35380: Have the images from docs/ref/contrib/admin/_images/ automatically generated.
#35380: Have the images from docs/ref/contrib/admin/_images/ automatically generated. ---------------
unread,
[Django] #35380: Have the images from docs/ref/contrib/admin/_images/ automatically generated.
#35380: Have the images from docs/ref/contrib/admin/_images/ automatically generated. ---------------
Apr 23
Django
12
Apr 23
[Django] #35189: Accessibility issues with collapsed fieldsets in admin forms
#35189: Accessibility issues with collapsed fieldsets in admin forms --------------------------------
unread,
[Django] #35189: Accessibility issues with collapsed fieldsets in admin forms
#35189: Accessibility issues with collapsed fieldsets in admin forms --------------------------------
Apr 23
Django
4
Apr 23
[Django] #35398: If the JSONField contains numbers key, the hash_key query becomes invalid
#35398: If the JSONField contains numbers key, the hash_key query becomes invalid -------------------
unread,
[Django] #35398: If the JSONField contains numbers key, the hash_key query becomes invalid
#35398: If the JSONField contains numbers key, the hash_key query becomes invalid -------------------
Apr 23
Django
Apr 23
Re: [Django] #35393: InlineAdmin's are not possible with an editable UUIDField as primary key. (was: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key.)
#35393: InlineAdmin's are not possible with an editable UUIDField as primary key. ---------------
unread,
Re: [Django] #35393: InlineAdmin's are not possible with an editable UUIDField as primary key. (was: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key.)
#35393: InlineAdmin's are not possible with an editable UUIDField as primary key. ---------------
Apr 23
Django
Apr 23
Re: [Django] #35378: Incorrect folding of long address headers with special characters when using 7bit Content-Transfer-Encoding in EmailMessage
#35378: Incorrect folding of long address headers with special characters when using 7bit Content-
unread,
Re: [Django] #35378: Incorrect folding of long address headers with special characters when using 7bit Content-Transfer-Encoding in EmailMessage
#35378: Incorrect folding of long address headers with special characters when using 7bit Content-
Apr 23
Django
20
Apr 23
Re: [Django] #12090: Show admin actions on the edit pages too
#12090: Show admin actions on the edit pages too -------------------------------------+--------------
unread,
Re: [Django] #12090: Show admin actions on the edit pages too
#12090: Show admin actions on the edit pages too -------------------------------------+--------------
Apr 23
Django
Apr 22
Re: [Django] #35394: Warning if `postgres` database has been renamed (e.g. DigitalOcean managed) (was: Warning if `postgres` database has been rename (e.g. DigitalOcean managed))
#35394: Warning if `postgres` database has been renamed (eg DigitalOcean managed) -------------------
unread,
Re: [Django] #35394: Warning if `postgres` database has been renamed (e.g. DigitalOcean managed) (was: Warning if `postgres` database has been rename (e.g. DigitalOcean managed))
#35394: Warning if `postgres` database has been renamed (eg DigitalOcean managed) -------------------
Apr 22
Django
Apr 22
Re: [Django] #35394: Warning if `postgres` database has been rename (e.g. DigitalOcean managed) (was: Warning if 'postgres' database has been rename (e.g. DigitalOcean managed))
#35394: Warning if `postgres` database has been rename (eg DigitalOcean managed) --------------------
unread,
Re: [Django] #35394: Warning if `postgres` database has been rename (e.g. DigitalOcean managed) (was: Warning if 'postgres' database has been rename (e.g. DigitalOcean managed))
#35394: Warning if `postgres` database has been rename (eg DigitalOcean managed) --------------------
Apr 22
Django
2
Apr 22
[Django] #35394: Warning if 'postgres' database has been rename (e.g. DigitalOcean managed)
#35394: Warning if 'postgres' database has been rename (eg DigitalOcean managed) ------------
unread,
[Django] #35394: Warning if 'postgres' database has been rename (e.g. DigitalOcean managed)
#35394: Warning if 'postgres' database has been rename (eg DigitalOcean managed) ------------
Apr 22
Django
7
Apr 22
[Django] #35392: aprefetch_related_objects cannot be imported from django.db.models
#35392: aprefetch_related_objects cannot be imported from django.db.models --------------------------
unread,
[Django] #35392: aprefetch_related_objects cannot be imported from django.db.models
#35392: aprefetch_related_objects cannot be imported from django.db.models --------------------------
Apr 22
Django
13
Apr 22
[Django] #34331: Support prefetch_related() with Queryset.aiterator()
#34331: Support prefetch_related() with Queryset.aiterator() -------------------------------------+--
unread,
[Django] #34331: Support prefetch_related() with Queryset.aiterator()
#34331: Support prefetch_related() with Queryset.aiterator() -------------------------------------+--
Apr 22
Django
3
Apr 22
[Django] #33852: Ability to exclude a specific view or form from DATA_UPLOAD_MAX_NUMBER_FIELDS
#33852: Ability to exclude a specific view or form from DATA_UPLOAD_MAX_NUMBER_FIELDS ---------------
unread,
[Django] #33852: Ability to exclude a specific view or form from DATA_UPLOAD_MAX_NUMBER_FIELDS
#33852: Ability to exclude a specific view or form from DATA_UPLOAD_MAX_NUMBER_FIELDS ---------------
Apr 22
Django
Apr 22
Re: [Django] #35395: slice filter crashes on an empty dict with Python 3.12 (was: Python 3.12 filter bug with Django 4.2.11)
#35395: slice filter crashes on an empty dict with Python 3.12 ---------------------------------+----
unread,
Re: [Django] #35395: slice filter crashes on an empty dict with Python 3.12 (was: Python 3.12 filter bug with Django 4.2.11)
#35395: slice filter crashes on an empty dict with Python 3.12 ---------------------------------+----
Apr 22
Django
5
Apr 22
[Django] #35395: Python 3.12 filter bug with Django 4.2.11
#35395: Python 3.12 filter bug with Django 4.2.11 ---------------------------------+-----------------
unread,
[Django] #35395: Python 3.12 filter bug with Django 4.2.11
#35395: Python 3.12 filter bug with Django 4.2.11 ---------------------------------+-----------------
Apr 22
Django
4
Apr 21
[Django] #35393: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key.
#35393: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key. -----------
unread,
[Django] #35393: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key.
#35393: InlineAdmin's are *not* possible with an *editable* UUIDField as primary key. -----------
Apr 21