Re: [Django] #31793: Async management command support

#31793: Async management command support -+- Reporter: James Pic|Owner: nobody Type: New feature | Status: closed Component: Core (Management

Re: [Django] #31833: FileField with a custom validator leads to "I/O operation on closed file". (was: Processing file from FileField with a custom class-based validator in a valid form leads to "I/O o

#31833: FileField with a custom validator leads to "I/O operation on closed file". -+--- Reporter: elmajax |Owner: Harpreet Sharma Type: Bug | Status: closed Component:

Re: [Django] #26624: Error when running sqlmigrate after dropping index (of index_together) without actually migrating

#26624: Error when running sqlmigrate after dropping index (of index_together) without actually migrating -+- Reporter: Akshesh Doshi|Owner: Type: Bug |

Re: [Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

#31834: Cannot sqlmigrate on Django migrations that change unique_together +-- Reporter: Brіаn Lаі |Owner: nobody Type: Bug | Status: closed Component: Migrations

Re: [Django] #29336: No docs for circular template inheritance

#29336: No docs for circular template inheritance -+- Reporter: Adrian Turjak|Owner: David Type: | Smith Cleanup/optimization |

Re: [Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

#31834: Cannot sqlmigrate on Django migrations that change unique_together -+- Reporter: Brіаn Lаі|Owner: nobody Type: Bug | Status: new C

Re: [Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

#31834: Cannot sqlmigrate on Django migrations that change unique_together -+- Reporter: Brіаn Lаі|Owner: nobody Type: Bug | Status: new C

Re: [Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

#31834: Cannot sqlmigrate on Django migrations that change unique_together -+- Reporter: Brіаn Lаі|Owner: nobody Type: Bug | Status: new C

[Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

#31834: Cannot sqlmigrate on Django migrations that change unique_together -+- Reporter: Brіаn Lаі | Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #31806: Make validators include the provided value in ValidationError

#31806: Make validators include the provided value in ValidationError -+- Reporter: Jon Dufresne |Owner: Jon | Dufresne Type: New feature

Re: [Django] #31806: Make validators include the provided value in ValidationError

#31806: Make validators include the provided value in ValidationError -+- Reporter: Jon Dufresne |Owner: Jon | Dufresne Type: New feature

Re: [Django] #31617: Improve overall admin accessibility.

#31617: Improve overall admin accessibility. -+- Reporter: Gustavo Siñovsky |Owner: (none) Type: New feature | Status: new Component: contrib.admin

Re: [Django] #31833: Processing file from FileField with a custom class-based validator in a valid form leads to "I/O operation on closed file" exception after posting (was: Processing file from FileF

#31833: Processing file from FileField with a custom class-based validator in a valid form leads to "I/O operation on closed file" exception after posting -+--- Reporter: elmajax |Owner: Harpreet Sharma

Re: [Django] #31617: Improve overall admin accessibility.

#31617: Improve overall admin accessibility. -+- Reporter: Gustavo Siñovsky |Owner: Abhishek | Bera Type: New feature | S

Re: [Django] #31833: Processing file from FileField in a valid form leads to "I/O operation on closed file" exception after posting

#31833: Processing file from FileField in a valid form leads to "I/O operation on closed file" exception after posting -+--- Reporter: elmajax |Owner: Harpreet Sharma Type: Bug |

[Django] #31833: Processing file from FileField in a valid form leads to "I/O operation on closed file" exception after posting

#31833: Processing file from FileField in a valid form leads to "I/O operation on closed file" exception after posting --+ Reporter: elmajax | Owner: nobody Type: Bug | Sta

Re: [Django] #30423: Make PasswordResetTokenGenerator's timeout extendable.

#30423: Make PasswordResetTokenGenerator's timeout extendable. +-- Reporter: Antoine Humeau |Owner: Antoine Humeau Type: New feature | Status: closed Component:

Re: [Django] #31832: PasswordResetTokenGenerator is difficult to extend

#31832: PasswordResetTokenGenerator is difficult to extend +-- Reporter: Iuri de Silvio |Owner: Iuri de Silvio Type: New feature | Status: closed Component: cont

Re: [Django] #31543: Default output buffering on in tests

#31543: Default output buffering on in tests -+- Reporter: Adam (Chainz)|Owner: Johnson| alyyasser19 Type: New feature | Stat

Re: [Django] #31832: PasswordResetTokenGenerator is difficult to extend

#31832: PasswordResetTokenGenerator is difficult to extend +-- Reporter: Iuri de Silvio |Owner: Iuri de Silvio Type: New feature | Status: closed Component: cont

[Django] #31832: PasswordResetTokenGenerator is difficult to extend

#31832: PasswordResetTokenGenerator is difficult to extend + Reporter: Iuri de Silvio| Owner: nobody Type: Cleanup/optimization | Status: new Compone

Re: [Django] #31832: PasswordResetTokenGenerator is difficult to extend

#31832: PasswordResetTokenGenerator is difficult to extend -+- Reporter: Iuri de Silvio |Owner: Iuri de Type: | Silvio Cleanup/optimization |

Re: [Django] #31806: Make validators include the provided value in ValidationError

#31806: Make validators include the provided value in ValidationError -+- Reporter: Jon Dufresne |Owner: Jon | Dufresne Type: New feature

Re: [Django] #31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup

#31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup -+- Reporter: sage |Owner: sage Type: Bug |