Re: [Django] #29865: Add XOR for use in Q Queries

#29865: Add XOR for use in Q Queries -+- Reporter: Griffith Rees|Owner: Ryan | Heard Type: New feature | Status:

[Django] #32899: enhance JSONResponse safe=True kwarg docs

#32899: enhance JSONResponse safe=True kwarg docs -+- Reporter: Thomas | Owner: Simon Willison Grainger | Type: | Status:

Re: [Django] #29865: Add XOR for use in Q Queries

#29865: Add XOR for use in Q Queries -+- Reporter: Griffith Rees|Owner: Ryan | Heard Type: New feature | Status:

Re: [Django] #32897: create_user() does not raise ValidationError

#32897: create_user() does not raise ValidationError --+-- Reporter: Adam McKay|Owner: nobody Type: Bug | Status: closed Component: contrib.auth |

Re: [Django] #32508: Raise proper exceptions instead of using "assert".

#32508: Raise proper exceptions instead of using "assert". --+ Reporter: Adam Johnson |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #32285: AppConfig.label should raise an exception when it's not a valid Python identifier.

#32285: AppConfig.label should raise an exception when it's not a valid Python identifier. -+- Reporter: Federico Capoano |Owner: Hasan Type: | Ramezani

Re: [Django] #32897: create_user() does not raise ValidationError

#32897: create_user() does not raise ValidationError --+-- Reporter: Adam McKay|Owner: nobody Type: Bug | Status: closed Component: contrib.auth |

Re: [Django] #32840: Micro-optimisation possibility in Field.get_col

#32840: Micro-optimisation possibility in Field.get_col -+- Reporter: Keryn Knight |Owner: Keryn Type: | Knight Cleanup/optimization |

Re: [Django] #32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known.

#32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known. -+- Reporter: Armin Stepanjan |Owner: Abhyudai Type:

Re: [Django] #32897: create_user() does not raise ValidationError

#32897: create_user() does not raise ValidationError --+-- Reporter: Adam McKay|Owner: nobody Type: Bug | Status: closed Component: contrib.auth |

Re: [Django] #32840: Micro-optimisation possibility in Field.get_col

#32840: Micro-optimisation possibility in Field.get_col -+- Reporter: Keryn Knight |Owner: Keryn Type: | Knight Cleanup/optimization |

Re: [Django] #30934: django.db.backends logging output should include the database alias

#30934: django.db.backends logging output should include the database alias -+- Reporter: David Winterbottom |Owner: Nick Pope Type: New feature | Status:

Re: [Django] #32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for well-formed values.

#32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for well-formed values. -+- Reporter: Keryn Knight |Owner: Keryn Type: | Knight

[Django] #32898: get_or_create() with filter() has surprising behaviour

#32898: get_or_create() with filter() has surprising behaviour --+ Reporter: Jamie Cockburn | Owner: nobody Type: Uncategorized | Status: new Component:

[Django] #32897: create_user() does not raise ValidationError

#32897: create_user() does not raise ValidationError + Reporter: adamckay | Owner: nobody Type: Bug | Status: new Component: contrib.auth |

Re: [Django] #28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page

#28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page -+- Reporter: Matt Westcott|Owner: cammil Type: Bug |

Re: [Django] #32896: Exclude on expressions not being negated as expected

#32896: Exclude on expressions not being negated as expected -+- Reporter: Alex Henman |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #30934: django.db.backends logging output should include the database alias

#30934: django.db.backends logging output should include the database alias -+- Reporter: David Winterbottom |Owner: Nick Pope Type: New feature | Status:

[Django] #32896: Exclude on expressions not being negated as expected

#32896: Exclude on expressions not being negated as expected -+- Reporter: Alex | Owner: nobody Henman | Type: Bug| Status: new

Re: [Django] #28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page

#28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page -+- Reporter: Matt Westcott|Owner: cammil Type: Bug |

Re: [Django] #26430: Coalesce in Aggregations ignored when EmptyResultSet returned

#26430: Coalesce in Aggregations ignored when EmptyResultSet returned -+- Reporter: Ryan Prater |Owner: Simon | Charette Type: Bug

Re: [Django] #26430: Coalesce in Aggregations ignored when EmptyResultSet returned

#26430: Coalesce in Aggregations ignored when EmptyResultSet returned -+- Reporter: Ryan Prater |Owner: Simon | Charette Type: Bug

Re: [Django] #32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known.

#32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known. -+- Reporter: Armin Stepanjan |Owner: Abhyudai Type:

Re: [Django] #32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known.

#32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known. -+- Reporter: Armin Stepanjan |Owner: Abhyudai Type:

Re: [Django] #32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known. (was: An exception should be raised when trying to save an aw

#32661: An exception should be raised when trying to save an aware datetime/time object even when the UTC offset isn't known. -+- Reporter: Armin Stepanjan |Owner: Abhyudai Type: