Re: [Django] #10961: Allow users to override forward and reverse relationships on proxy models with !ForeignKey fields.

[Django]

#10961: Allow users to override forward and reverse relationships on proxy 
models
with !ForeignKey fields.
-+-
 Reporter:  Tai Lee  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy ForeignKey | Triage Stage:  Accepted
  reverse relationship manager   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by powderflask):

 I've run up against this issue on several projects, in fact nearly every
 time I use proxy models to solve a problem.  Different workarounds each
 time, depending on use-case.
 Currently working with M2M relations on proxy models, same issue can
 occur.
 This is solved nicely with prefetch_related using a Prefetch object, and
 specifying the queryset from the related proxy model.

 {{{
 prefetch=models.Prefetch('related_set',
 queryset=RelatedProxyModel.objects.all())
 obj = MyModel.objects.prefetch_related(prefetch).first()
 assert all( [type(r) == RelatedProxyModel for r in obj.related_set.all()]
 )
 }}}

 The same approach should work for accessing a reverse relation.
 This can all be hidden in a model Manager or Queryset to make code
 prettier.

 Got me to wonder if a similar approach could be used by allowing a
 queryset to be specified on select_related?  In fact, only need the model
 class, since a queryset for select_related would over-specify.
 Not as elegant as a declaration on the model, but seems like it might be
 pretty flexible and if it's easy to implement, a quick-and-dirty work-
 around that avoids any hackery.

-- 
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.ae5fdcb74f1657aed7d2daf89f330f45%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
---+--
Changes (by Niccolò Mineo):

 * type:  Uncategorized => New feature


-- 
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.426e74983770dc468e0e224cd8901593%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:  Uncategorized  |   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
---+--
Changes (by Niccolò Mineo):

 * has_patch:  0 => 1


-- 
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.57539ebada6daf190786fc7c2f12ebad%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:  Uncategorized  |   Status:  new
Component:  contrib.redirects  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  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.

New 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.

--

-- 
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.f4f57cd1e0b2a8c0efeaefd797d78206%40djangoproject.com.

Re: [Django] #27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() and tearDownClass() (was: LiveServerPort test methods set allow_thread_sharing to False before all server thr

[Django]

#27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() 
and
tearDownClass()
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * owner:  (none) => Jacob Walls
 * status:  new => assigned
 * type:  Bug => Cleanup/optimization


Comment:

 > Back to the original state of play after changes in #28478.

 Actually, not quite the original state of play. `allow_thread_sharing` was
 removed in #30171 in favor of a counter pattern which obviates the
 reported bug here. I still think Chris's suggestion has value, but it's
 more of a cleanup opportunity, if I'm not mistaken.

 Having touched this a couple times I ought to just finish it off.

-- 
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.47bc605491afa277bd70d3f91a630350%40djangoproject.com.

[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:  Uncategorized  | Status:  new
  Component:  contrib.redirects  |Version:  3.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 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.

-- 
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/055.b122e57c2155600a635085faf0398cb8%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:  assigned
Component:  Documentation  |  Version:  3.2
 Severity:  Normal |   Resolution:
 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 Nick Frazier):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15001 PR]

-- 
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.f09094c634e9f8f69c38ce13220ca863%40djangoproject.com.

[Django] #33205: call_command fails when required mutually exclusive group arguments use the same `dest`

[Django]

#33205: call_command fails when required mutually exclusive group arguments use 
the
same `dest`
-+
   Reporter:  Peter Law  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  3.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I have a command which accepts two different ways to specify a time --
 either as a timestamp or as a duration in the future:
 {{{
 pause (--for duration | --until time)
 }}}

 {{{#!python
 class Command(BaseCommand):
 def add_arguments(self, parser) -> None:
 group = parser.add_mutually_exclusive_group(required=True)
 group.add_argument('--for', dest='until', action='store',
 type=parse_duration_to_time)
 group.add_argument('--until', action='store', type=parse_time)

 def handle(self, until: datetime, **_):
 pass
 }}}


 This works fine on the command line, however there doesn't seem to be a
 way to make this work through `call_command`. Specifically there are two
 sides to the failure:
 - while I can provide an `until` value (as a string, which is processed by
 `parse_time`) there is no mechanism to pass a `for` value if that's how I
 want to spell the input
 - the `for` value is always required and attempts to parse the (string)
 `until` value passed, which then errors since the input formats are very
 different

-- 
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/053.b7bde51b8d74330c4899df9e1d26929d%40djangoproject.com.

Re: [Django] #16406: Allow separate access to matches from urlpatterns and extra_context args

[Django]

#16406: Allow separate access to matches from urlpatterns and extra_context args
-+-
 Reporter:  Florian Apolloner|Owner:  Anvesh
 Type:   |  Mishra
  Cleanup/optimization   |   Status:  assigned
Component:  Core (URLs)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  resolvers, reverse   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Anvesh Mishra):

 * owner:  Alexandre Prieto Pantoja => Anvesh Mishra


-- 
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/066.2ed43cf7f564593d15d7b262d22c4dfc%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:  4.0
  (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 Jacob Walls):

 * has_patch:  0 => 1


-- 
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.92d072a43f70696db68d488b5967878f%40djangoproject.com.

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

[Django]

#33203: OrderedSet should inherit from collections.abc.MutableSet
+--
 Reporter:  kumaraditya303  |Owner:  kumaraditya303
 Type:  Uncategorized   |   Status:  assigned
Component:  Utilities   |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham):

 You should describe the rationale in the ticket description.

-- 
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.ce567ba07209f69de3f7e37b3fce3a2f%40djangoproject.com.

Re: [Django] #33204: Make MultiValueDict more consistent

[Django]

#33204: Make MultiValueDict more consistent
+--
 Reporter:  Yaroslav Pankovych  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  HTTP handling   |  Version:  3.2
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  Core (Other) => HTTP handling


Comment:

 Thanks for the suggestion, however I don't think it's worth breaking
 backwards compatibility. We need to reach a strong consensus on the
 DevelopersMailingList before moving it forward. Please
 [https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
 tickets/#closing-tickets follow the triaging guidelines with regards to
 wontfix tickets] and take this to DevelopersMailingList.

-- 
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/068.8c0601ab596acb828c2f3e233dd3%40djangoproject.com.

Re: [Django] #33202: Add a "grouper" template filter

[Django]

#33202: Add a "grouper" template filter
-+--
 Reporter:  horpto   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * version:   => dev
 * resolution:   => wontfix


Comment:

 The current thread is to keep Django a core framework, not providing every
 utility which might be useful. You can write that filter in your own
 library. You can start a discussion on DevelopersMailingList if you don't
 agree.

-- 
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.6a280954db07997e2879fcaa2bcbdb76%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:  assigned
Component:  Documentation  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Nick Frazier):

 * owner:  nobody => Nick Frazier
 * status:  new => assigned


Comment:

 Will submit a PR for this later today.

-- 
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.9c87cee1abbafcaf24ea67674eeaf222%40djangoproject.com.

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

[Django]

#33203: OrderedSet should inherit from collections.abc.MutableSet
+--
 Reporter:  kumaraditya303  |Owner:  kumaraditya303
 Type:  Uncategorized   |   Status:  assigned
Component:  Utilities   |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by kumaraditya303):

 https://github.com/django/django/pull/15000

-- 
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.f55742e31c92b9045e08c892b6df3a41%40djangoproject.com.

Re: [Django] #33204: Make MultiValueDict more consistent

[Django]

#33204: Make MultiValueDict more consistent
+--
 Reporter:  Yaroslav Pankovych  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  3.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by Yaroslav Pankovych):

 * cc: Yaroslav Pankovych (added)
 * needs_docs:  0 => 1


Comment:

 https://github.com/django/django/pull/14945

-- 
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/068.ab989ee0a2d7129e117a4c4ae559b85c%40djangoproject.com.

[Django] #33204: Make MultiValueDict more consistent

[Django]

#33204: Make MultiValueDict more consistent
--+
   Reporter:  Yaroslav Pankovych  |  Owner:  nobody
   Type:  New feature | Status:  new
  Component:  Core (Other)|Version:  3.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 I was working with query parameters and found that `.pop()` and `.get()`
 both have different logic.

 I assume that `.pop()` should be the same as `.get()`, but the key should
 get deleted afterward.

 Here's an example:

 {{{
 In [1]: from django.utils.datastructures import MultiValueDict

 In [2]: data = MultiValueDict({"name": ["Yaroslav", "Clara"], "age": [22,
 32]})

 In [3]: data.get("name")
 Out[3]: 'Clara'

 In [4]: data.pop("name")
 Out[4]: ['Yaroslav', 'Clara']
 }}}


 As you can see, we've got a single item for `.get()`, and a list for
 `.pop()`, which is confusing.

 We should have all of that synced. `.get()` with `.getlist()`, and
 `.pop()` with `.poplist()`.

 Here's how it looks like after I've done some changes:

 {{{
 In [4]: data.pop("name")
 Out[4]: 'Clara'
 }}}


 {{{
 In [5]: data.poplist("name")
 Out[5]: ['Yaroslav', 'Clara']
 }}}


 This is breaking change probably.

-- 
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/053.92bad723ba6a7f4579ae8472175274ca%40djangoproject.com.

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

[Django]

#33203: OrderedSet should inherit from collections.abc.MutableSet
--+
   Reporter:  kumaraditya303  |  Owner:  kumaraditya303
   Type:  Uncategorized   | Status:  assigned
  Component:  Utilities   |Version:  dev
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  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/057.853574b6ad189c2a93ab15a564e49584%40djangoproject.com.

[Django] #33202: Add a "grouper" template filter

[Django]

#33202: Add a "grouper" template filter
---+
   Reporter:  horpto   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Template system  |Version:
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 A simple filter tag that will get an iterableof elements and optional
 number n. It will regroup an iterable to iterable of lists with length not
 more than n elements. By default n is 2.
 This filter can be used to render lists to rows.

 `[3,4,5,6,7,8,9]| grouper -> [[3, 4], [5, 6], [7, 8], [9]]`

-- 
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/049.d523ef045d7da69c828939afc13ab151%40djangoproject.com.

Re: [Django] #33201: RenameModel with db_table should be a noop. (was: RenameModel with db_table recreate constraints.)

[Django]

#33201: RenameModel with db_table should be a noop.
-+-
 Reporter:  Iuri de Silvio   |Owner:  Iuri de
 Type:   |  Silvio
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   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):

 * has_patch:  0 => 1
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/14999 PR]

-- 
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/068.f3ff90165fb1e9ea228325c7a5dd802a%40djangoproject.com.

Re: [Django] #33201: RenameModel with db_table recreate constraints.

[Django]

#33201: RenameModel with db_table recreate constraints.
+--
 Reporter:  Iuri de Silvio  |Owner:  Iuri de Silvio
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  3.2
 Severity:  Normal  |   Resolution:
 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 Iuri de Silvio):

 * owner:  nobody => Iuri de Silvio
 * status:  new => assigned


-- 
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/068.2c2e72f6284a190cfd9166c7b67c99d4%40djangoproject.com.

[Django] #33201: RenameModel with db_table recreate constraints.

[Django]

#33201: RenameModel with db_table recreate constraints.
--+
   Reporter:  Iuri de Silvio  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  3.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 A RenameModel operation that already has db_table defined must be a noop.

 In Postgres, it drops and recreates foreign key constraints. In sqlite it
 recreates the table (as expected for a table renaming).

-- 
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/053.bb3c4c359c6c5b311684315bef9c42f9%40djangoproject.com.