django-updates
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10.
Django
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10.
Django
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10.
Django
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10.
Django
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10.
Django
Re: [Django] #36812: Drop support for MariaDB 10.6-10.10. (was: Drop support for MariaDB 10.6.)
Django
[Django] #36812: Drop support for MariaDB 10.6.
Django
Re: [Django] #36770: SQLite threading tests are flaky when parallel test suite runs in forkserver mode (was: SQLite threading tests are flaky when parallel test suite runs in forkserver/spawn)
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #30515: Document django.shortcuts.resolve_url.
Django
Re: [Django] #36809: Allow EmailValidator to customize error messages depending on the part that failed validation (was: Allow EmailValidator to return 'domain_part' in ValidationError params)
Django
[Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
Re: [Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
Re: [Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
Re: [Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
Re: [Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
Re: [Django] #36811: Admin timezone warning shows incorrect plural form and confusing message
Django
[Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36810: SimpleLazyObject.__repr__ causes infinite recursion when setup function is a bound method
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #36600: Misleading wording in description of dispatch_uid
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #36436: Sensitive signer.key exposed via Django messages framework in templates
Django
[Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
Re: [Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
Re: [Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
Re: [Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
Re: [Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
Re: [Django] #36809: Allow EmailValidator to return 'domain_part' in ValidationError params
Django
[Django] #36808: Make UniqueConstraint name required in signature
Django
Re: [Django] #36808: Make UniqueConstraint name required in signature
Django
Re: [Django] #36808: Make UniqueConstraint name required in signature
Django
Re: [Django] #36808: Make UniqueConstraint name required in signature
Django
Re: [Django] #36808: Make UniqueConstraint name required in signature
Django
Re: [Django] #36027: ASGI: Dead persistent postgres connections are not closed when the database is accessed in response_for_exception
Django
Re: [Django] #36027: ASGI: Dead persistent postgres connections are not closed when the database is accessed in response_for_exception
Django
Re: [Django] #36027: ASGI: Dead persistent postgres connections are not closed when the database is accessed in response_for_exception
Django
Re: [Django] #36376: Use argparse colorized help on Python 3.14+
Django
Re: [Django] #36376: Use argparse colorized help on Python 3.14+
Django
Re: [Django] #36790: Add a generic error view handler
Django
[Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36807: Admin fieldset field layout issue in the Safari browser.
Django
Re: [Django] #36594: Clarify UniqueConstraint's nulls_distinct system check warning
Django
Re: [Django] #36594: Clarify UniqueConstraint's nulls_distinct system check warning
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition
Django
Re: [Django] #36806: Add system check for null kwarg in GeneratedField definition (was: GeneratedField with null=False creates nullable column on MySQL)
Django
Re: [Django] #36806: GeneratedField with null=False creates nullable column on MySQL
Django
Re: [Django] #36806: GeneratedField with null=False creates nullable column on MySQL (was: GeneratedField with null=False creates nullable column on MySQL with spatial types (POINT))
Django
[Django] #36806: GeneratedField with null=False creates nullable column on MySQL with spatial types (POINT)
Django
[Django] #36805: Use `None` as default value for `from_email` in `send_mail`-function
Django
Re: [Django] #36805: Use `None` as default value for `from_email` in `send_mail`-function
Django
Re: [Django] #36805: Use `None` as default value for `from_email` in `send_mail`-function
Django
[Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
Re: [Django] #36804: AdminSite.get_model_admin raises AttributeError when `to` model of a ForeignKey is defined as a string
Django
[Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
Re: [Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
Re: [Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
Re: [Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
Re: [Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
Re: [Django] #36803: Make AlterField a no-op when ManyToManyField's through.db_table remains the same between renames.
Django
[Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36802: ManyToManyField Table name changed (django 5.2 > django 6.0)
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
Re: [Django] #36608: Clarify dumpdata behavior and docs for custom serializers with internal_use_only flag
Django
[Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36801: `construct_change_message`call `form.changed_data` after check if is add
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
[Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
Re: [Django] #36800: Issue with ManyToManyField renaming
Django
[Django] #36799: Create a how-to on how to test a pre-release version of Django
Django
Re: [Django] #36799: Create a how-to on how to test a pre-release version of Django
Django
Re: [Django] #36799: Create a how-to on how to test a pre-release version of Django
Django
Re: [Django] #35838: Support Requests with Transfer-Encoding: Chunked
Django
Re: [Django] #35838: Support Requests with Transfer-Encoding: Chunked
Django
Re: [Django] #17752: Serialization and multi-table inheritance
Django
Re: [Django] #17752: Serialization and multi-table inheritance
Django
[Django] #36798: TypeError: MultilingualQuerySet._update() takes 2 positional arguments but 3 were given when saving model with 'update_fiels' argument
Django
Re: [Django] #36798: TypeError: MultilingualQuerySet._update() takes 2 positional arguments but 3 were given when saving model with 'update_fiels' argument
Django
Re: [Django] #36235: RelatedManager.all().get_or_create() does not work
Django
Re: [Django] #36235: RelatedManager.all().get_or_create() does not work
Django
Re: [Django] #36235: RelatedManager.all().get_or_create() does not work
Django
Re: [Django] #36235: RelatedManager.all().get_or_create() does not work
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include
Django
Re: [Django] #36796: URL resolution breaks if route defined with lazy string and uses an include (was: gettext_lazy and url patterns)
Django
[Django] #36797: Implement fully async-capable support for django.middleware.common.CommonMiddleware
Django
Re: [Django] #36797: Implement fully async-capable support for django.middleware.common.CommonMiddleware
Django
Re: [Django] #36797: Implement fully async-capable support for django.middleware.common.CommonMiddleware
Django
[Django] #36796: gettext_lazy and url patterns
Django
Re: [Django] #36796: gettext_lazy and url patterns
Django
Re: [Django] #14645: Exclude query with multiple conditions for the same multi-value relation not correct
Django
Re: [Django] #14645: Exclude query with multiple conditions for the same multi-value relation not correct
Django
Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated
Django
Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated
Django
Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated
Django
Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated
Django
Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated
Django
Earlier messages
Later messages