django-updates
Thread
Date
Earlier messages
Messages by Thread
Re: [Django] #36198: Unique Constraints defined with __date lookups on F expressions fail validation but create database constraints sucessfully
Django
Re: [Django] #36079: Size of the object's str in TabularInline is too small
Django
Re: [Django] #36079: Size of the object's str in TabularInline is too small
Django
Re: [Django] #35911: FilteredSelectMultiple Widget Not Functional in Inline Formset After Form Deletion
Django
[Django] #36538: Addition of `AdminSite.media` for adding JS and CSS files globally to every admin page
Django
Re: [Django] #36538: Addition of `AdminSite.media` for adding JS and CSS files globally to every admin page
Django
[Django] #36537: Generate unique IDs for the OSM layer mapwidget options `json_script` tags
Django
Re: [Django] #36537: Generate unique IDs for the OSM layer mapwidget options `json_script` tags
Django
Re: [Django] #36537: Generate unique IDs for the OSM layer mapwidget options `json_script` tags
Django
Re: [Django] #36537: Generate unique IDs for the OSM layer mapwidget options `json_script` tags
Django
Re: [Django] #34871: Validation of UniqueConstraint with Case() crashes.
Django
Re: [Django] #34871: Validation of UniqueConstraint with Case() crashes.
Django
Re: [Django] #34871: Validation of UniqueConstraint with Case() crashes.
Django
Re: [Django] #34871: Validation of UniqueConstraint with Case() crashes.
Django
Re: [Django] #30618: AppConfig.name should be a full python path when using the optional directory.
Django
Re: [Django] #30618: AppConfig.name should be a full python path when using the optional directory.
Django
Re: [Django] #30618: AppConfig.name should be a full python path when using the optional directory.
Django
Re: [Django] #30618: AppConfig.name should be a full python path when using the optional directory.
Django
[Django] #36536: Creating nested app using startapp should use full Python path for AppConfig.name
Django
Re: [Django] #36536: Creating nested app using startapp should use full Python path for AppConfig.name
Django
Re: [Django] #36536: Creating nested app using startapp should use full Python path for AppConfig.name
Django
Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.
Django
Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.
Django
Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.
Django
Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.
Django
[Django] #36535: Ensure compatibility with docutils 0.19 through 0.22+ in admindocs
Django
Re: [Django] #36535: Ensure compatibility with docutils 0.19 through 0.22+ in admindocs
Django
Re: [Django] #36535: Ensure compatibility with docutils 0.19 through 0.22+ in admindocs
Django
Re: [Django] #36535: Ensure compatibility with docutils 0.19 through 0.22+ in admindocs
Django
[Django] #36534: Problem Statement: Spike in PostgreSQL Connections After Upgrading Django from 3.2 to 5.2 Despite CONN_MAX_AGE = 10
Django
Re: [Django] #36534: Problem Statement: Spike in PostgreSQL Connections After Upgrading Django from 3.2 to 5.2 Despite CONN_MAX_AGE = 10
Django
[Django] #36533: manage.py startapp <name> <directory> fails to create new app
Django
Re: [Django] #36533: manage.py startapp <name> <directory> fails to create new app
Django
Re: [Django] #36533: manage.py startapp <name> <directory> fails to create new app
Django
Re: [Django] #14092: ImageField should allow SVG
Django
[Django] #36532: Add Content Security Policy (CSP) view decorators
Django
Re: [Django] #36532: Add Content Security Policy (CSP) view decorators
Django
Re: [Django] #36532: Add Content Security Policy (CSP) view decorators
Django
Re: [Django] #36532: Add Content Security Policy (CSP) view decorators
Django
Re: [Django] #35119: Unify max_length for EmailValidator and model's and form's EmailField
Django
Re: [Django] #35119: Unify max_length for EmailValidator and model's and form's EmailField
Django
[Django] #36531: Add "forkserver" support to parallel test runner.
Django
Re: [Django] #36531: Add "forkserver" support to parallel test runner.
Django
Re: [Django] #36531: Add "forkserver" support to parallel test runner.
Django
Re: [Django] #36531: Add "forkserver" support to parallel test runner.
Django
Re: [Django] #36531: Add "forkserver" support to parallel test runner.
Django
Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings.
Django
Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings.
Django
Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings.
Django
Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings.
Django
Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings. (was: Allow for annoying runserver development server warning to be silenced via settings.)
Django
Re: [Django] #31202: Bulk update suffers from poor performance with large numbers of models and columns
Django
Re: [Django] #31202: Bulk update suffers from poor performance with large numbers of models and columns
Django
[Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
Re: [Django] #36530: System check for ManyToManyField & Composite Primary Key checks only one direction
Django
[Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
Re: [Django] #36529: Improvement of the filter and model selection sidebar on the admin changelist page for mobile screens.
Django
[Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
Re: [Django] #36528: When "view_on_site" is set to True, the rendered button has an underline.
Django
[Django] #36527: Allow for annoying runserver development server warning to be silenced via settings.
Django
Re: [Django] #35442: N+1 queries from RelatedManager + only("pk")
Django
Re: [Django] #35442: N+1 queries from RelatedManager + only("pk")
Django
[Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #36526: bulk_update uses more memory than expected
Django
Re: [Django] #26583: Increase the vebosity at which collectstatic warns for conflicting destination paths (was: Increase vebosity at collectstatic warns for conflicting destination paths)
Django
Re: [Django] #26583: Increase vebosity at collectstatic warns for conflicting destination paths (was: Add an option to silence collectstatic clashing files warnings)
Django
Re: [Django] #36525: The default verbosity of collectstatic --clear is too verbose
Django
Re: [Django] #36525: The default verbosity of collectstatic --clear is too verbose
Django
Re: [Django] #35892: Support Widget.use_fieldset in admin forms
Django
Re: [Django] #35892: Support Widget.use_fieldset in admin forms
Django
Re: [Django] #35892: Support Widget.use_fieldset in admin forms
Django
Re: [Django] #35892: Support Widget.use_fieldset in admin forms
Django
Re: [Django] #35892: Support Widget.use_fieldset in admin forms
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #2259: Primary keys should be readonly by default in admin
Django
Re: [Django] #36525: The default verbosity of collectstatic --clear is too verbose (was: The default verbosity of collectstatic --clear is to verbose)
Django
[Django] #36525: The default verbosity of collectstatic --clear is to verbose
Django
Re: [Django] #34563: ManifestStaticFilesStorage support for CSS module scripts in Javascript files.
Django
Re: [Django] #35371: False positive in JS module aggregation export regex when an export declaration precedes an import declaration
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions
Django
Re: [Django] #36522: Tuple lookups cannot handle right-hand sides mixing literal values and expressions (was: Assigning expressions to model fields does not work if the field participates in a composite primary key)
Django
Re: [Django] #28200: Do not touch hash-designated files which already exist at the destination storage
Django
Re: [Django] #27929: Add ManifestStaticFilesStorage option to remove original (non-hashed) files after processing
Django
[Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
Re: [Django] #36524: EmailMessage method documentation cannot be cross referenced
Django
[Django] #36523: Implement helper method to find module path of value
Django
Re: [Django] #36523: Implement helper method to find module path of value
Django
Re: [Django] #36523: Implement helper method to find module path of value
Django
Re: [Django] #30577: Custom rendering for readonly fields in admin
Django
[Django] #36522: Assigning expressions to model fields does not work if the field participates in a composite primary key
Django
Re: [Django] #36522: Assigning expressions to model fields does not work if the field participates in a composite primary key
Django
Re: [Django] #30577: Custom rendering for readonly fields in admin (was: feature request: custom rendering for readonly fields in admin)
Django
Re: [Django] #25263: How closely we should adhere to PEP 257
Django
Re: [Django] #30577: feature request: custom rendering for readonly fields in admin
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #35514: Dictionary based EMAIL_PROVIDERS settings
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression
Django
Re: [Django] #36518: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression (was: full_clean crashes on model with both a CheckConstraint and a GeneratedField with a Case expression (possible regression in Django 5.2))
Django
[Django] #36521: Proposal: Add Static Type Annotations to Django Core (Phase-wise Plan)
Django
Re: [Django] #36521: Proposal: Add Static Type Annotations to Django Core (Phase-wise Plan)
Django
[Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
Re: [Django] #36520: Performance Regression in parse_header_params
Django
[Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Re: [Django] #36519: The center template filter is inconsistent when adding an odd amount of padding
Django
Earlier messages