Re: [Django] #29562: An idea for improving the template fragment cache

#29562: An idea for improving the template fragment cache -+- Reporter: HongWeipeng |Owner: nobody Type: New feature | Status: new Component: Core

Re: [Django] #29425: Auto language redirect does not work if prefix_default_language=False in root URLConf

#29425: Auto language redirect does not work if prefix_default_language=False in root URLConf -+- Reporter: Nathan Humphreys |Owner: nobody Type: Bug |

[Django] #29562: An idea for improving the template fragment cache

#29562: An idea for improving the template fragment cache ---+ Reporter: HongWeipeng | Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #23976: ValidationError crashes if initialized with a list of empty dicts

#23976: ValidationError crashes if initialized with a list of empty dicts -+- Reporter: archivarius888 |Owner: nobody Type: | Status: new

Re: [Django] #29123: Changing an IntegerField to a ForeignKey generates incorrectly ordered migration operations if the field is in unique_together

#29123: Changing an IntegerField to a ForeignKey generates incorrectly ordered migration operations if the field is in unique_together +- Reporter: Ed Morley |Owner: (none) Type: Bug |

Re: [Django] #28862: Removing a field from index_together/unique_together and from the model generates a migration that crashes

#28862: Removing a field from index_together/unique_together and from the model generates a migration that crashes ---+ Reporter: Artem Maslovskiy |Owner: Jeff Type: Bug|

Re: [Django] #21442: Configurable request parsing.

#21442: Configurable request parsing. ---+ Reporter: Tom Christie |Owner: Tom Christie Type: New feature| Status: assigned Component: HTTP handling |

Re: [Django] #29542: Annotated field created by subquery, referenced inside of F() generates invalid SQL

#29542: Annotated field created by subquery, referenced inside of F() generates invalid SQL -+- Reporter: Joey Wilhelm |Owner: felixxm Type: Bug |

Re: [Django] #29560: Add an option to django-admin to always colorize output

#29560: Add an option to django-admin to always colorize output -+- Reporter: Nicolas Noé |Owner: Nicolas | Noé Type: New feature |

Re: [Django] #29561: Window Function Lag/Lead supported on Filter (Not equal) for FloatField

#29561: Window Function Lag/Lead supported on Filter (Not equal) for FloatField -+- Reporter: Gabriel Oliveira |Owner: nobody Type: Uncategorized| Status:

Re: [Django] #29561: Window Function Lag/Lead supported on Filter (Not equal) for FloatField

#29561: Window Function Lag/Lead supported on Filter (Not equal) for FloatField -+- Reporter: Gabriel Oliveira |Owner: nobody Type: Uncategorized| Status:

Re: [Django] #29560: Add an option to django-admin to always colorize output

#29560: Add an option to django-admin to always colorize output -+- Reporter: Nicolas Noé |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #29560: Add an option to django-admin to always colorize output

#29560: Add an option to django-admin to always colorize output -+- Reporter: Nicolas Noé |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #29560: Add an option to django-admin to always colorize output

#29560: Add an option to django-admin to always colorize output -+- Reporter: Nicolas Noé |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #28598: BCC addresses are ignored in the console and file email backends

#28598: BCC addresses are ignored in the console and file email backends -+- Reporter: zngr |Owner: Josh Type: | Schneier Cleanup/optimization

Re: [Django] #28598: BCC addresses are ignored in the console and file email backends

#28598: BCC addresses are ignored in the console and file email backends -+- Reporter: zngr |Owner: Josh Type: | Schneier Cleanup/optimization