Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

#29998: pk setup for MTI to parent get confused by multiple OneToOne references. -+- Reporter: Mārtiņš Šulcs|Owner: felixxm Type: Bug | Status:

Re: [Django] #31162: GIS error logging when using WKT string as input to filter() query.

#31162: GIS error logging when using WKT string as input to filter() query. + Reporter: Arno|Owner: felixxm Type: Bug | Status: assigned Component: GIS |

Re: [Django] #31162: GIS error logging when using WKT string as input to filter() query.

#31162: GIS error logging when using WKT string as input to filter() query. + Reporter: Arno|Owner: (none) Type: Bug | Status: new Component: GIS |

Re: [Django] #31162: GIS error logging when using WKT string as input to filter() query.

#31162: GIS error logging when using WKT string as input to filter() query. + Reporter: Arno|Owner: dbxnr Type: Bug | Status: assigned Component: GIS |

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. ---+ Reporter: Brandon Navra |Owner: nobody Type: New feature|

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug |

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug |

Re: [Django] #31122: Clarify how the Lookup class follow the Query Expression API.

#31122: Clarify how the Lookup class follow the Query Expression API. -+- Reporter: Hongtao Ma |Owner: Rohit Jha Type: | Status: assigned

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

#29998: pk setup for MTI to parent get confused by multiple OneToOne references. -+- Reporter: Mārtiņš Šulcs|Owner: felixxm Type: Bug | Status:

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

#31124: Model.get_FOO_display() does not work correctly with inherited choices. -+- Reporter: Yash Jhunjhunwala|Owner: Carlton | Gibson Type: Bug

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

#31124: Model.get_FOO_display() does not work correctly with inherited choices. -+- Reporter: Yash Jhunjhunwala|Owner: Carlton | Gibson Type: Bug

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

#29998: pk setup for MTI to parent get confused by multiple OneToOne references. -+- Reporter: Mārtiņš Šulcs|Owner: felixxm Type: Bug | Status:

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

#29998: pk setup for MTI to parent get confused by multiple OneToOne references. -+- Reporter: Mārtiņš Šulcs|Owner: felixxm Type: Bug | Status:

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

#29998: pk setup for MTI to parent get confused by multiple OneToOne references. -+- Reporter: Mārtiņš Šulcs|Owner: felixxm Type: Bug | Status:

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

#31124: Model.get_FOO_display() does not work correctly with inherited choices. -+- Reporter: Yash Jhunjhunwala|Owner: Carlton | Gibson Type: Bug

Re: [Django] #27468: Move utils.crypto.salted_hmac() from SHA1 toward SHA256

#27468: Move utils.crypto.salted_hmac() from SHA1 toward SHA256 -+- Reporter: Tim Graham |Owner: Claude Type: | Paroz Cleanup/optimization |

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

#31124: Model.get_FOO_display() does not work correctly with inherited choices. -+- Reporter: Yash Jhunjhunwala|Owner: Carlton | Gibson Type: Bug

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

#31124: Model.get_FOO_display() does not work correctly with inherited choices. -+- Reporter: Yash Jhunjhunwala|Owner: George | Popides Type: Bug

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. ---+ Reporter: Brandon Navra |Owner: nobody Type: New feature|

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. ---+ Reporter: Brandon Navra |Owner: nobody Type: New feature|

Re: [Django] #31163: Use filters after when case, the table is not reused. (was: use filters after when case, the table is not reused.)

#31163: Use filters after when case, the table is not reused. -+- Reporter: Ashe |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. ---+ Reporter: Brandon Navra |Owner: nobody Type: New feature|

Re: [Django] #23051: QuerySet.only() fail to work with reverse o2o relationships

#23051: QuerySet.only() fail to work with reverse o2o relationships -+- Reporter: Vladimir Dmitriev|Owner: Paulo Type: Bug | Status: assigned

Re: [Django] #31165: Overhaul settings.

#31165: Overhaul settings. --+-- Reporter: orlnub123 |Owner: nobody Type: Bug | Status: closed Component: Core (Other) | Version: master

Re: [Django] #31136: Multiple annotations with Exists() should not group by aliases.

#31136: Multiple annotations with Exists() should not group by aliases. -+- Reporter: Sigurd Ljødal|Owner: felixxm Type: Bug | Status: closed

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. (was: Parallel test mode not working on MacOS with recent versions of Python 3)

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method. ---+ Reporter: Brandon Navra |Owner: nobody Type: New feature|

Re: [Django] #28297: Same queryset result in two different queries on ORM. (was: Same queryset result in two different queries on ORM)

#28297: Same queryset result in two different queries on ORM. -+- Reporter: Marcus Renno |Owner: Marcus | Renno Type: Bug |

Re: [Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 ---+-- Reporter: Brandon Navra |Owner: nobody Type: Bug| Status: new

Re: [Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 ---+-- Reporter: Brandon Navra |Owner: nobody Type: Bug| Status: new

Re: [Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 ---+-- Reporter: Brandon Navra |Owner: nobody Type: Bug| Status: new

Re: [Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 ---+-- Reporter: Brandon Navra |Owner: nobody Type: Bug| Status: new

Re: [Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 ---+-- Reporter: Brandon Navra |Owner: nobody Type: Bug| Status: new

[Django] #31169: Parallel test mode not working on MacOS with recent versions of Python 3

#31169: Parallel test mode not working on MacOS with recent versions of Python 3 -+ Reporter: Brandon Navra | Owner: nobody Type: Bug| Status: new

Re: [Django] #31136: Multiple annotations with Exists() should not group by aliases.

#31136: Multiple annotations with Exists() should not group by aliases. -+- Reporter: Sigurd Ljødal|Owner: felixxm Type: Bug | Status: new

Re: [Django] #31136: Multiple annotations with Exists() should not group by aliases.

#31136: Multiple annotations with Exists() should not group by aliases. -+- Reporter: Sigurd Ljødal|Owner: felixxm Type: Bug | Status: new

Re: [Django] #29177: Unmanaged models with ForeignKeys do not get those fields serialized into their migration state when CreateModel happens.

#29177: Unmanaged models with ForeignKeys do not get those fields serialized into their migration state when CreateModel happens. --+ Reporter: Keryn Knight |Owner: nobody Type: Bug |

Re: [Django] #31166: Provide context for ImproperlyConfigured exceptions in URL resolver.

#31166: Provide context for ImproperlyConfigured exceptions in URL resolver. -+- Reporter: Ram Rachum |Owner: Ram Type: | Rachum Cleanup/optimization