Re: [Django] #31371: Increase the length of the User model's first_name field to 150 characters

#31371: Increase the length of the User model's first_name field to 150 characters --+ Reporter: Ryan Petrello |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31372: autoreload: dictionary changed size during iteration

#31372: autoreload: dictionary changed size during iteration -+- Reporter: minusf |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #10919: Add an option to disable display of related items on admin's delete confirmation page (to prevent large memory usage on complex objects)

#10919: Add an option to disable display of related items on admin's delete confirmation page (to prevent large memory usage on complex objects) + Reporter: Tobias McNulty |Owner: nobody

Re: [Django] #31371: Increase the length of the User model's first_name field to 150 characters

#31371: Increase the length of the User model's first_name field to 150 characters -+- Reporter: Ryan Petrello|Owner: Ryan Type: | Petrello

[Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections -+ Reporter: Marcin Nowak | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31372: autoreload: dictionary changed size during iteration

#31372: autoreload: dictionary changed size during iteration -+- Reporter: minusf |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: nobody Type: | Status: new Cleanup/optimization |

[Django] #31371: Increase the length of the User model's first_name field to 150 characters

#31371: Increase the length of the User model's first_name field to 150 characters + Reporter: Ryan Petrello | Owner: nobody Type: Cleanup/optimization | Status:

[Django] #31372: autoreload: dictionary changed size during iteration

#31372: autoreload: dictionary changed size during iteration -+- Reporter: minusf | Owner: nobody Type: Bug| Status: new Component: Core |

Re: [Django] #31372: autoreload: dictionary changed size during iteration

#31372: autoreload: dictionary changed size during iteration -+- Reporter: minusf |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: hristiy4n Type: | Status: assigned Cleanup/optimization

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: hristiy4n Type: | Status: assigned Cleanup/optimization

[Django] #31374: Runtime Error unable to solve from forums/ FAQ

#31374: Runtime Error unable to solve from forums/ FAQ -+- Reporter: l_sharma | Owner: nobody Type: | Status: new Uncategorized |

Re: [Django] #31374: Runtime Error unable to solve from forums/ FAQ. (was: Runtime Error unable to solve from forums/ FAQ)

#31374: Runtime Error unable to solve from forums/ FAQ. -+- Reporter: l_sharma |Owner: nobody Type: Uncategorized| Status: closed Component:

Re: [Django] #31372: Autoreload: dictionary changed size during iteration. (was: autoreload: dictionary changed size during iteration)

#31372: Autoreload: dictionary changed size during iteration. --+-- Reporter: minusf|Owner: nobody Type: Bug | Status: closed Component: Core (Other) |

Re: [Django] #31172: Note that yesno can be affected by extra spaces in translations.

#31172: Note that yesno can be affected by extra spaces in translations. -+- Reporter: José Antonio Ruiz|Owner: Hasan | Ramezani Type: Bug

Re: [Django] #26993: Increase the length of the User model's last_name field to 150 characters

#26993: Increase the length of the User model's last_name field to 150 characters -+- Reporter: Malcolm Box |Owner: Thom Type: | Wiggers

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

[Django] #31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST)

#31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST) -+- Reporter: Simon | Owner: nobody Charette |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

[Django] #31375: make_password shouldn't accept values other than bytes or string as an argument

#31375: make_password shouldn't accept values other than bytes or string as an argument + Reporter: iamdavidcz| Owner: nobody Type: Bug | Status: new

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31368: Document Field.from_db_value()'s "expression" parameter.

#31368: Document Field.from_db_value()'s "expression" parameter. -+- Reporter: Paolo Lammens|Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: Hristiyan Type: | Ivanov Cleanup/optimization | Status:

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #31375: make_password shouldn't accept values other than bytes or string as an argument

#31375: make_password shouldn't accept values other than bytes or string as an argument --+-- Reporter: iamdavidcz|Owner: nobody Type: Bug | Status: new

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections ---+-- Reporter: Marcin Nowak |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31375: make_password shouldn't accept values other than bytes or string as an argument

#31375: make_password shouldn't accept values other than bytes or string as an argument --+-- Reporter: iamdavidcz|Owner: nobody Type: Bug | Status: new

Re: [Django] #31368: Document Field.from_db_value()'s "expression" parameter.

#31368: Document Field.from_db_value()'s "expression" parameter. -+- Reporter: Paolo Lammens|Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections -+- Reporter: Marcin Nowak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections -+- Reporter: Marcin Nowak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST)

#31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST) -+- Reporter: Simon Charette |Owner: nobody Type:

Re: [Django] #31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST). (was: Avoid unnecessary null checks ordering when possible on database that

#31376: Avoid unnecessary null checks ordering when possible on database that don't support NULLS (FIRST|LAST). -+- Reporter: Simon Charette |Owner: Simon Type:

Re: [Django] #31373: Django 3.x / uwsgi is leaking connections

#31373: Django 3.x / uwsgi is leaking connections -+- Reporter: Marcin Nowak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: nobody Type: | Status: closed Cleanup/optimization |

[Django] #31370: Make parallel test runner work with buffer option

#31370: Make parallel test runner work with buffer option -+- Reporter: Adam | Owner: nobody (Chainz) Johnson | Type: New| Status:

Re: [Django] #31370: Make parallel test runner work with buffer option. (was: Make parallel test runner work with buffer option)

#31370: Make parallel test runner work with buffer option. -+- Reporter: Adam (Chainz)|Owner: nobody Johnson| Type: New feature |

Re: [Django] #31370: Make parallel test runner work with buffer option.

#31370: Make parallel test runner work with buffer option. -+- Reporter: Adam (Chainz)|Owner: nobody Johnson| Type: New feature |

Re: [Django] #31370: Make parallel test runner work with buffer option.

#31370: Make parallel test runner work with buffer option. -+- Reporter: Adam (Chainz)|Owner: nobody Johnson| Type: New feature |

Re: [Django] #31370: Make parallel test runner work with buffer option.

#31370: Make parallel test runner work with buffer option. -+- Reporter: Adam (Chainz)|Owner: Adam Johnson| (Chainz) Johnson Type: New feature

Re: [Django] #31224: Add asynchronous views.

#31224: Add asynchronous views. -+- Reporter: felixxm |Owner: Andrew | Godwin Type: New feature | Status:

Re: [Django] #31369: Deprecate NullBooleanField

#31369: Deprecate NullBooleanField -+- Reporter: David Smith |Owner: nobody Type: | Status: new Cleanup/optimization |

Re: [Django] #31360: Is `request.csrf_processing_done` part of the public CSRF protection API?

#31360: Is `request.csrf_processing_done` part of the public CSRF protection API? -+- Reporter: Jaap Roes|Owner: nobody Type: | Status:

Re: [Django] #31172: Note that yesno can be affected by extra spaces in translations.

#31172: Note that yesno can be affected by extra spaces in translations. -+- Reporter: José Antonio Ruiz|Owner: Hasan | Ramezani Type: Bug