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

[Django]

#33194: Remaking table with unique constraint crashes on SQLite.
-+-
 Reporter:  Mark |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.a9c885b1700ab31f563db56bb468365e%40djangoproject.com.

Re: [Django] #33198: BinaryField documentation references length in characters, which is incorrect

[Django]

#33198: BinaryField documentation references length in characters, which is
incorrect
---+
 Reporter:  Gavin Wahl |Owner:  Nick Frazier
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  3.2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Mariusz Felisiak ):

 In [changeset:"fdc1c6435c8fb9e720169ef0aebf87c33f1d86c2" fdc1c64]:
 {{{
 #!CommitTicketReference repository=""
 revision="fdc1c6435c8fb9e720169ef0aebf87c33f1d86c2"
 [3.2.x] Fixed #33198 -- Corrected BinaryField.max_length docs.

 Backport of 0d4e575c96d408e0efb4dfd0cbfc864219776950 from main
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f480f2f5ce05d8aed8c66f81c2e1d742%40djangoproject.com.

Re: [Django] #33198: BinaryField documentation references length in characters, which is incorrect

[Django]

#33198: BinaryField documentation references length in characters, which is
incorrect
---+
 Reporter:  Gavin Wahl |Owner:  Nick Frazier
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  3.2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Mariusz Felisiak ):

 In [changeset:"f5fd03aebe54f28a62436ef81aeed50fef594619" f5fd03ae]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5fd03aebe54f28a62436ef81aeed50fef594619"
 [4.0.x] Fixed #33198 -- Corrected BinaryField.max_length docs.

 Backport of 0d4e575c96d408e0efb4dfd0cbfc864219776950 from main
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dfe32589c9ef539ef269b09d4f0beddb%40djangoproject.com.

Re: [Django] #33198: BinaryField documentation references length in characters, which is incorrect

[Django]

#33198: BinaryField documentation references length in characters, which is
incorrect
---+
 Reporter:  Gavin Wahl |Owner:  Nick Frazier
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  3.2
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0d4e575c96d408e0efb4dfd0cbfc864219776950" 0d4e575c]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d4e575c96d408e0efb4dfd0cbfc864219776950"
 Fixed #33198 -- Corrected BinaryField.max_length docs.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6761b5184c375f2405cd2fc5b97a888f%40djangoproject.com.

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

[Django]

#33194: Remaking table with unique constraint crashes on SQLite.
-+-
 Reporter:  Mark |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * version:  4.0 => 3.2


Comment:

 > Not really sure if we need a backport to 3.2 but feels like this would
 create issues for non-unique functional indexes on SQLite as well.

 Good catch, it's a bug in 83fcfc9ec8610540948815e127101f1206562ead.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.a1a895df98baf86b248cc2285e4c4b68%40djangoproject.com.

Re: [Django] #33203: OrderedSet should inherit from collections.abc.MutableSet

[Django]

#33203: OrderedSet should inherit from collections.abc.MutableSet
-+-
 Reporter:  kumaraditya303   |Owner:
 Type:   |  kumaraditya303
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  dev
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  assigned => closed
 * type:  Uncategorized => Cleanup/optimization
 * resolution:   => needsinfo


Comment:

 > You should describe the rationale in the ticket description.

 Yes. Moreover, I don't see how `OrderedSet` implements `MutableSet` as
 described in [https://www.python.org/dev/peps/pep-3119/#sets PEP 3119].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.f8d4796330b7e8e853d4d04c2ad56915%40djangoproject.com.

Re: [Django] #33206: Allow redirect type choice in contrib.redirects app

[Django]

#33206: Allow redirect type choice in contrib.redirects app
-+-
 Reporter:  Niccolò Mineo|Owner:  Niccolò
 |  Mineo
 Type:  New feature  |   Status:  assigned
Component:  contrib.redirects|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Adam Johnson (added)
 * needs_better_patch:  0 => 1
 * status:  new => assigned
 * owner:  nobody => Niccolò Mineo
 * stage:  Unreviewed => Accepted


Comment:

 Thank for this proposition. Tentatively accepted, but only to allow
 redirect type change (301, 302, 307, 308) per a redirect instance. PR
 contains unrelated and backward incompatible changes e.g. swapping the
 redirect model or a new behavior for `410 ("Gone")` redirects.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.d4f2340bc4ee00512b28b29429d5d267%40djangoproject.com.

Re: [Django] #33206: Allow redirect type choice in contrib.redirects app

[Django]

#33206: Allow redirect type choice in contrib.redirects app
---+--
 Reporter:  Niccolò Mineo  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.redirects  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Niccolò Mineo:

Old description:

> I would like to propose allowing the user to choose the redirect type
> (301, 302 and 410 by default) when adding a redirect in the
> contrib.redirects app admin site.
> [https://github.com/django/django/pull/15002 PR] is here.

New description:

 As [https://groups.google.com/g/django-developers/c/c_ghDNzAN50 originally
 discussed], I would like to propose allowing the user to choose the
 redirect type (301, 302 and 410 by default) when adding a redirect in the
 contrib.redirects app admin site.
 [https://github.com/django/django/pull/15002 PR] is here.

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.eb9e8f1fa5589d985042c8297ab8d4f3%40djangoproject.com.

Re: [Django] #25916: Add lastmod support to sitemapindex

[Django]

#25916: Add lastmod support to sitemapindex
--+---
 Reporter:  Matthew Downey|Owner:  David Smith
 Type:  New feature   |   Status:  assigned
Component:  contrib.sitemaps  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  sitemap lastmod   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by David Smith):

 * needs_better_patch:  1 => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3d5b5b468e40d649947e106f78955d74%40djangoproject.com.