Re: [Django] #33194: Remaking table with unique constraint crashes on SQLite.

#33194: Remaking table with unique constraint crashes on SQLite. -+- Reporter: Mark |Owner: Hannes | Ljungberg Type: Bug

Re: [Django] #33194: Remaking table with unique constraint crashes on SQLite.

#33194: Remaking table with unique constraint crashes on SQLite. -+- Reporter: Mark |Owner: Hannes | Ljungberg Type: Bug

Re: [Django] #33172: Document CBV decoration for modifying upload handlers on the fly

#33172: Document CBV decoration for modifying upload handlers on the fly -+- Reporter: Matthew Pava |Owner: SREEHARI Type: | K.V Cleanup/optimization

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. +-- Reporter: Daniel Samuels |Owner: Daniel Samuels Type: New feature | Status: assigned Component: Core (Other)

Re: [Django] #33197: Renaming field and providing prior field name to db_column should be an SQL noop

#33197: Renaming field and providing prior field name to db_column should be an SQL noop -+- Reporter: Jacob Walls |Owner: Simon Type: | Charette Cleanup/op

Re: [Django] #33197: Renaming field and providing prior field name to db_column should be an SQL noop

#33197: Renaming field and providing prior field name to db_column should be an SQL noop --+ Reporter: Jacob Walls |Owner: nobody Type: Cleanup/optimization | S

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. +-- Reporter: Daniel Samuels |Owner: Daniel Samuels Type: New feature | Status: assigned Component: Core (Other)

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. + Reporter: Daniel Samuels |Owner: nobody Type: New feature | Status: new Component: Core (Other)|

Re: [Django] #33197: Renaming field and providing prior field name to db_column should be an SQL noop

#33197: Renaming field and providing prior field name to db_column should be an SQL noop --+ Reporter: Jacob Walls |Owner: nobody Type: Cleanup/optimization | S

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. + Reporter: Daniel Samuels |Owner: nobody Type: New feature | Status: new Component: Core (Other)|

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. + Reporter: Daniel Samuels |Owner: nobody Type: New feature | Status: new Component: Core (Other)|

Re: [Django] #33200: Consider "hiding" datetime/zoneinfo imports in django.utils.timezone

#33200: Consider "hiding" datetime/zoneinfo imports in django.utils.timezone -+- Reporter: Jaap Roes|Owner: nobody Type: | Status: closed

Re: [Django] #33199: Make Signer parameters keyword-only.

#33199: Make Signer parameters keyword-only. + Reporter: Daniel Samuels |Owner: nobody Type: New feature | Status: new Component: Core (Other)|

Re: [Django] #33199: Make Signer parameters keyword-only. (was: Consider making Signer parameters keyword-only)

#33199: Make Signer parameters keyword-only. + Reporter: Daniel Samuels |Owner: nobody Type: New feature | Status: new Component: Core (Other)|

[Django] #33200: Consider "hiding" datetime/zoneinfo imports in django.utils.timezone

#33200: Consider "hiding" datetime/zoneinfo imports in django.utils.timezone -+- Reporter: Jaap Roes | Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #33199: Consider making Signer parameters keyword-only

#33199: Consider making Signer parameters keyword-only --+ Reporter: Daniel Samuels | Owner: nobody Type: New feature | Status: new Component: Core (Other)|

Re: [Django] #32074: Python 3.10 compatibility

#32074: Python 3.10 compatibility -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | Status:

Re: [Django] #32074: Python 3.10 compatibility

#32074: Python 3.10 compatibility -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | Status:

Re: [Django] #32074: Python 3.10 compatibility

#32074: Python 3.10 compatibility -+- Reporter: Mariusz Felisiak |Owner: Mariusz | Felisiak Type: New feature | Status:

Re: [Django] #33192: It is not possible to use a custom lookup/transorm in a CheckConstraint

#33192: It is not possible to use a custom lookup/transorm in a CheckConstraint -+- Reporter: Fabien MICHEL|Owner: nobody Type: Bug | Status: clos

Re: [Django] #33195: Class-based urlize()

#33195: Class-based urlize() -+- Reporter: Claude Paroz |Owner: Claude Type: | Paroz Cleanup/optimization | Status: closed

Re: [Django] #33195: Class-based urlize()

#33195: Class-based urlize() -+- Reporter: Claude Paroz |Owner: Claude Type: | Paroz Cleanup/optimization | Status: assigned