Re: [Django] #35762: SQLite deprecating double-quotes for string literals

#35762: SQLite deprecating double-quotes for string literals -+- Reporter: Geoff Fellows|Owner: Claude | Paroz Type: Bug |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +-- Reporter: Richard Laager |Owner: (none) Type: Bug | Status: new Component: contrib.admin |

[Django] #35769: Multiline fields display wrong in tablet/phone sizes

#35769: Multiline fields display wrong in tablet/phone sizes +- Reporter: Richard Laager | Type: Bug Status: new |Component: contrib.admin Version: 4.2

Re: [Django] #35763: Setting the auto increment value of a database model breaks when you add a new field to the model

#35763: Setting the auto increment value of a database model breaks when you add a new field to the model -+- Reporter: Kevin Renskers |Owner: MrInfaith Type: Bug |

Re: [Django] #35735: For python 3.9+ class property may not be accessible by Django's template system

#35735: For python 3.9+ class property may not be accessible by Django's template system -+- Reporter: Fabian Braun |Owner: Fabian | Braun Type:

Re: [Django] #33095: Admin actions shown with zero results

#33095: Admin actions shown with zero results -+- Reporter: Richard Laager |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #35742: Apply UserAdmin add_form_template according to User model USERNAME_FIELD

#35742: Apply UserAdmin add_form_template according to User model USERNAME_FIELD -+- Reporter: antoliny0919 |Owner: Type: | antoliny0919 Cleanup/optimization

Re: [Django] #35758: Use keyword argument rather than a positional argument for on_delete in the ForeignKey.on_delete docs.

#35758: Use keyword argument rather than a positional argument for on_delete in the ForeignKey.on_delete docs. -+- Reporter: kay |Owner: kay Type: |

Re: [Django] #35758: Use keyword argument rather than a positional argument for on_delete in the ForeignKey.on_delete docs.

#35758: Use keyword argument rather than a positional argument for on_delete in the ForeignKey.on_delete docs. -+- Reporter: kay |Owner: (none) Type: |

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35074: Altering spatial_index does not actually create/drop the index

#35074: Altering spatial_index does not actually create/drop the index --+ Reporter: Mário Falcão |Owner: Mariusz Felisiak Type: Bug | Status: assigned Comp

Re: [Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton Gibson |Owner: Carlton Type: | Gibson Cleanup/optimization | St

Re: [Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton Gibson |Owner: Carlton Type: | Gibson Cleanup/optimization | St

Re: [Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton Gibson |Owner: Carlton Type: | Gibson Cleanup/optimization | St

Re: [Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton Gibson |Owner: Carlton Type: | Gibson Cleanup/optimization | St

Re: [Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton Gibson |Owner: Carlton Type: | Gibson Cleanup/optimization | St

Re: [Django] #2750: ManyToManyField ignores 'default' option

#2750: ManyToManyField ignores 'default' option -+- Reporter: bangcok_dangerus@… |Owner: Wim | Feijen Type: Bug | S

Re: [Django] #35768: Add a User Profile How-To to docs (was: Add a Profile How-To)

#35768: Add a User Profile How-To to docs -+- Reporter: Carlton Gibson |Owner: William | S. Vincent Type: New feature |

Re: [Django] #35768: Add a Profile How-To

#35768: Add a Profile How-To -+- Reporter: Carlton Gibson |Owner: William | S. Vincent Type: New feature | Status: ass

[Django] #35768: Add a Profile How-To

#35768: Add a Profile How-To -+- Reporter: Carlton| Owner: William S. Vincent Gibson | Type: New| Status: assigned feature

[Django] #35767: Adjust customizing user model docs

#35767: Adjust customizing user model docs -+- Reporter: Carlton| Owner: Carlton Gibson Gibson | Type: | Status: assigned Cle

Re: [Django] #35680: Add default automatic imports to shell

#35680: Add default automatic imports to shell -+- Reporter: Salvo Polizzi|Owner: Salvo | Polizzi Type: New feature |

Re: [Django] #35766: Choice iterator breaks when using slices

#35766: Choice iterator breaks when using slices ---+-- Reporter: David |Owner: (none) Type: Uncategorized | Status: new Component: Uncategorized |

[Django] #35766: Choice iterator breaks when using slices

#35766: Choice iterator breaks when using slices ---+- Reporter: David | Type: Uncategorized Status: new|Component: Uncategorized Version: 5.0| Severity:

Re: [Django] #35742: Apply UserAdmin add_form_template according to User model USERNAME_FIELD

#35742: Apply UserAdmin add_form_template according to User model USERNAME_FIELD -+- Reporter: antoliny0919 |Owner: Type: | antoliny0919 Cleanup/optimization

Re: [Django] #35074: Altering spatial_index does not actually create/drop the index

#35074: Altering spatial_index does not actually create/drop the index --+ Reporter: Mário Falcão |Owner: Mariusz Felisiak Type: Bug | Status: assigned Comp

Re: [Django] #34887: Allow unlimited CharField for SQLite backend

#34887: Allow unlimited CharField for SQLite backend -+- Reporter: Kar Petrosyan|Owner: Jae Hyuck | Sa Type: New feature |

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35103: UniqueConstraint message does not use violation_error_message

#35103: UniqueConstraint message does not use violation_error_message -+- Reporter: Gerben Morsink |Owner: Gerben Type: | Morsink Cleanup/optimization

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35762: SQLite deprecating double-quotes for string literals

#35762: SQLite deprecating double-quotes for string literals -+- Reporter: Geoff Fellows|Owner: Claude | Paroz Type: Bug |

Re: [Django] #34221: Plural-Forms in .po files break Django's translation precedence.

#34221: Plural-Forms in .po files break Django's translation precedence. -+- Reporter: Stefano Parmesan |Owner: Claude | Paroz Type: Bug

Re: [Django] #34221: Plural-Forms in .po files break Django's translation precedence.

#34221: Plural-Forms in .po files break Django's translation precedence. -+- Reporter: Stefano Parmesan |Owner: Claude | Paroz Type: Bug

Re: [Django] #34887: Allow unlimited CharField for SQLite backend

#34887: Allow unlimited CharField for SQLite backend -+- Reporter: Kar Petrosyan|Owner: Jae Hyuck | Sa Type: New feature |

Re: [Django] #34887: Allow unlimited CharField for SQLite backend

#34887: Allow unlimited CharField for SQLite backend -+- Reporter: Kar Petrosyan|Owner: Jae Hyuck | Sa Type: New feature |

Re: [Django] #34887: Allow unlimited CharField for SQLite backend

#34887: Allow unlimited CharField for SQLite backend -+- Reporter: Kar Petrosyan|Owner: Kar | Petrosyan Type: New feature |

Re: [Django] #35759: Don't require max_length on CharField on SQLite backend

#35759: Don't require max_length on CharField on SQLite backend -+- Reporter: Curtis Maloney |Owner: Jae Hyuck | Sa Type: New feature |

Re: [Django] #28215: sensitive_post_parameters/sensitive_variables leaking sensitive values into the http 500 exception email

#28215: sensitive_post_parameters/sensitive_variables leaking sensitive values into the http 500 exception email -+- Reporter: Peter Zsoldos|Owner: Calvin Vu Type: Bug |

Re: [Django] #35761: When switching which field is `primary_key`, migrations do not seem to handle multiple `auto` columns

#35761: When switching which field is `primary_key`, migrations do not seem to handle multiple `auto` columns -+- Reporter: Jonas Vacek |Owner: (none) Type: Bug |

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35765: Change label of list_display with __ lookup to only show the bit after the __

#35765: Change label of list_display with __ lookup to only show the bit after the __ +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed

Re: [Django] #35764: Maybe add links to tickets and/or PRs in the release notes

#35764: Maybe add links to tickets and/or PRs in the release notes +-- Reporter: Kevin Renskers |Owner: (none) Type: Uncategorized | Status: closed Component: Document