Re: [Django] #32820: Fields’ errors should be programmatically associated with fields.

[Django]

#32820: Fields’ errors should be programmatically associated with fields.
-+-
 Reporter:  Thibaud Colas|Owner:  David
 |  Smith
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility, ui,   | Triage Stage:  Accepted
  forms  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"10725a31879c55ba8d92aaa3275093d136957bef" 10725a3]:
 {{{
 #!CommitTicketReference repository=""
 revision="10725a31879c55ba8d92aaa3275093d136957bef"
 Fixed #32820 -- Added aria-invalid="true" to fields with errors.

 Co-authored-by: Demetris Stavrou 
 Co-authored-by: David Smith 
 }}}

-- 
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/01070189afae0553-c771f3b6-7c14-43da-9a09-5f284815b962-00%40eu-central-1.amazonses.com.

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

[Django]

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
-+
 Reporter:  Chris Woytowitz  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  dev
 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
-+

Comment (by Roberto Maurizzi):

 Just hit the same problem after renaming a Model and creating a new one
 with the old name (to conform to how several other models in that
 application ended up being named).

 I was able to fix it by:
  - changing the new Model creation in the migration to specify
 `spatial_index=False` (it was a GIS field, I guess for regular ones you
 need to use `db_index=False`)
  - running makemigrations again: since I never changed the models, it
 detected the missing indexes and created another migration that added them
 to the db

 This worked both for migrating the production database (was working
 earlier too) and when running tests.

-- 
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/01070189af7e576f-6ceed60e-8e3f-43c2-8d37-6e193f0fef84-00%40eu-central-1.amazonses.com.

Re: [Django] #34750: Fixed QuerySet.count() on querysets grouped by unused multi-valued annotations.

[Django]

#34750: Fixed QuerySet.count() on querysets grouped by unused multi-valued
annotations.
-+-
 Reporter:  Toan Vuong   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.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):

 * 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/01070189af2cfe3e-cb95a54a-df54-48f9-9e07-4cf10d8d49fc-00%40eu-central-1.amazonses.com.

Re: [Django] #34331: Support prefetch_related() with Queryset.aiterator()

[Django]

#34331: Support prefetch_related() with Queryset.aiterator()
-+-
 Reporter:  Barry Johnson|Owner:  john-
 |  parton
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 ):

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


Comment:

 In [changeset:"fff14736f1cc594f79ea0e2656b8375d837b7aca" fff1473]:
 {{{
 #!CommitTicketReference repository=""
 revision="fff14736f1cc594f79ea0e2656b8375d837b7aca"
 Fixed #34331 -- Added QuerySet.aiterator() support for prefetch_related().
 }}}

-- 
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/01070189ad89f709-f4fc7534-daf4-431d-a04f-21085a21352e-00%40eu-central-1.amazonses.com.

Re: [Django] #22055: 404 page does not display stack trace when Resolver404 is raised from a view

[Django]

#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
-+-
 Reporter:  Grzegorz Nosek   |Owner:  Andrew
 Type:   |  Northall
  Cleanup/optimization   |   Status:  assigned
Component:  Core (URLs)  |  Version:  dev
 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
-+-

Comment (by Natalia Bidart):

 I'm not sure if it's too late to propose to "unaccept" this ticket. I have
 read the use case, and while there is a description for a use case, that
 use case feels, to me, insufficient to make a strong argument to add this
 change of behavior in the django codebase.

 My rationale is that failing to resolve an URL in a view is, indeed,
 semantically an "url not found" (404) result. At least in my experience, I
 can think of a few reasons for a failed resolve in a view such as:

   * there is a spelling error in the url name or args (in which case the
 unit tests should caught this)
   * there is a dynamic component in the url name/params that at the time
 of the execution evaluates to something that does not exist (this still
 feels like a 404 and not a 500)
   * something else I'm missing?

 I don't think the above justify the complexity that seems to be necessary
 to solve this (following [https://github.com/django/django/pull/17007 PR
 17007]).

-- 
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/01070189ad6d01d0-38372126-200e-4cdf-b07e-c737e03691cb-00%40eu-central-1.amazonses.com.

Re: [Django] #34331: Support prefetch_related() with Queryset.aiterator()

[Django]

#34331: Support prefetch_related() with Queryset.aiterator()
-+-
 Reporter:  Barry Johnson|Owner:  john-
 |  parton
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   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):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_docs:  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/01070189ad63664e-af73ebf6-3716-4799-a6bb-b68283cac2a1-00%40eu-central-1.amazonses.com.

Re: [Django] #34210: Show the duration of individual tests

[Django]

#34210: Show the duration of individual tests
-+-
 Reporter:  Paolo Melchiorre |Owner:  David
 |  Smith
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  test, timing,| Triage Stage:  Accepted
  durations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * needs_better_patch:  0 => 1


Comment:

 Setting the flag "patch needs improvement" to remove this work from the
 review queue (and also because the branch will need a rebase and conflict
 fixes before landing).

-- 
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/01070189ad5c35b8-4ab8b164-fa06-40fa-8d1f-a0e8aca6f21f-00%40eu-central-1.amazonses.com.

Re: [Django] #34542: Required fields allowed to be blank are not accepted non-interactively using createsuperuser

[Django]

#34542: Required fields allowed to be blank are not accepted non-interactively
using createsuperuser
-+-
 Reporter:  Lantizia |Owner:  Mateusz
 |  Więckowski
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  auth | Triage Stage:  Accepted
  createsuperuser superuser email|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * needs_better_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/01070189ad380794-a6d00288-e779-452d-b492-3aa9db2d2aed-00%40eu-central-1.amazonses.com.

Re: [Django] #34655: Tests for RadioSelect and Select have diverged considerably, potentially leaving RadioSelect undertested

[Django]

#34655: Tests for RadioSelect and Select have diverged considerably, potentially
leaving RadioSelect undertested
-+-
 Reporter:  Natalia Bidart   |Owner:  Jacob1507
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  4.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"1ad7761ee616341295f36c80f78b86ff79d5b513" 1ad7761]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ad7761ee616341295f36c80f78b86ff79d5b513"
 Refs #34655 -- Made cosmetic edits to RadioSelect tests.

 Follow up to f9c5958b8fe452983122b6a13c8f806e4e4e1eef.
 }}}

-- 
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/01070189ad2b3374-b00c5a52-c7bf-4cbc-8cdf-5a95d6fdb087-00%40eu-central-1.amazonses.com.

Re: [Django] #34542: Required fields allowed to be blank are not accepted non-interactively using createsuperuser

[Django]

#34542: Required fields allowed to be blank are not accepted non-interactively
using createsuperuser
-+-
 Reporter:  Lantizia |Owner:  Mateusz
 |  Więckowski
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  auth | Triage Stage:  Accepted
  createsuperuser superuser email|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateusz Więckowski):

 * owner:  Anvansh Singh => Mateusz Więckowski
 * 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/01070189ace9b529-cc1601b7-5a21-475a-8d61-5cee6907cf5b-00%40eu-central-1.amazonses.com.

Re: [Django] #34331: Support prefetch_related() with Queryset.aiterator()

[Django]

#34331: Support prefetch_related() with Queryset.aiterator()
-+-
 Reporter:  Barry Johnson|Owner:  john-
 |  parton
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by john-parton):

 Updated my pull request

-- 
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/01070189ac904baa-4e86f510-5da5-4cb1-af2a-a4823dec06c1-00%40eu-central-1.amazonses.com.

Re: [Django] #34746: High CPU/memory consumption when a 5XX is raised with large local variables

[Django]

#34746: High CPU/memory consumption when a 5XX is raised with large local 
variables
-+-
 Reporter:  Rémi Dupré   |Owner:  Vishesh
 Type:   |  Garg
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/17127 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/01070189ac41afb3-6f56f00f-96b2-49bc-9a67-ced51eb7654f-00%40eu-central-1.amazonses.com.

Re: [Django] #34586: create() does not save reverse OneToOne relationship nor raise an Exception

[Django]

#34586: create() does not save reverse OneToOne relationship nor raise an 
Exception
-+-
 Reporter:  Alan Rivas   |Owner:  Mariana
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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):

 * needs_better_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/01070189ac3c8cbb-a590e2d3-8475-4ac6-80de-0ab55a902d95-00%40eu-central-1.amazonses.com.

Re: [Django] #34586: create() does not save reverse OneToOne relationship nor raise an Exception

[Django]

#34586: create() does not save reverse OneToOne relationship nor raise an 
Exception
-+-
 Reporter:  Alan Rivas   |Owner:  Mariana
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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 Mariana):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17112 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/01070189ac30141b-26626a9c-2ad0-4dee-9616-2132a64733c2-00%40eu-central-1.amazonses.com.

Re: [Django] #34750: Fixed QuerySet.count() on querysets grouped by unused multi-valued annotations.

[Django]

#34750: Fixed QuerySet.count() on querysets grouped by unused multi-valued
annotations.
-+-
 Reporter:  Toan Vuong   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 I've prepared a regression test:
 {{{#!diff
 diff --git a/tests/aggregation/tests.py b/tests/aggregation/tests.py
 index 9f2a7c8841..8bdeaca97d 100644
 --- a/tests/aggregation/tests.py
 +++ b/tests/aggregation/tests.py
 @@ -2165,6 +2165,25 @@ class AggregateAnnotationPruningTests(TestCase):
  self.assertEqual(sql.count("select"), 2, "Subquery wrapping
 required")
  self.assertNotIn("authors_count", sql)

 +def test_unused_aliased_aggregate_and_annotation_reverse_fk(self):
 +Book.objects.create(
 +name="b3",
 +publisher=self.p2,
 +pages=1000,
 +rating=4.2,
 +price=50,
 +contact=self.a2,
 +pubdate=datetime.date.today(),
 +)
 +qs = Publisher.objects.annotate(
 +total_pages=Sum("book__pages"),
 +good_book=Case(
 +When(book__rating__gt=4.0, then=Value(True)),
 +default=Value(False),
 +),
 +)
 +self.assertEqual(qs.count(), 3)
 +
  def test_non_aggregate_annotation_pruned(self):
  with CaptureQueriesContext(connection) as ctx:
  Book.objects.annotate(

 }}}

-- 
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/01070189abb970d6-e3b442a9-25ed-4cf4-96cf-94c440100ea4-00%40eu-central-1.amazonses.com.

Re: [Django] #34331: Support prefetch_related() with Queryset.aiterator()

[Django]

#34331: Support prefetch_related() with Queryset.aiterator()
-+-
 Reporter:  Barry Johnson|Owner:  john-
 |  parton
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_docs:  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/01070189ab67fd29-93abdcfd-2f05-4700-9325-a1a83d413f61-00%40eu-central-1.amazonses.com.

Re: [Django] #18830: FormWizard with Formset and Form Fields mixed on same page

[Django]

#18830: FormWizard with Formset and Form Fields mixed on same page
-+--
 Reporter:  jeff@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 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:  new => closed
 * resolution:   => wontfix
 * stage:  Accepted => Unreviewed


Comment:

 The idea behind this feature is quite fuzzy. It sounds like a third-party
 package is the best way to proceed as it doesn't need to be included in
 Django itself.

-- 
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/01070189ab4018d7-24ba98e0-8e14-4d11-bd91-af7bdcd2cdbe-00%40eu-central-1.amazonses.com.

Re: [Django] #33143: Block import-time queries

[Django]

#33143: Block import-time queries
-+-
 Reporter:  Adam Johnson |Owner:  Florian
 Type:   |  Zimmermann
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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):

 * needs_better_patch:  0 => 1


Comment:

 Marking as need improvement per Adam's
 [https://github.com/django/django/pull/16923#discussion_r1278985276
 comment].

-- 
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/01070189ab38f519-6acb36e1-e06b-4fc6-b381-ac53c1c83ac3-00%40eu-central-1.amazonses.com.

Re: [Django] #34692: django.forms.renderers.get_default_renderer()'s template loader cache is not being reset on autoloads.

[Django]

#34692: django.forms.renderers.get_default_renderer()'s template loader cache is
not being reset on autoloads.
+---
 Reporter:  Andrew  |Owner:  Priyank Panchal
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by Mariusz Felisiak):

 * 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/01070189ab356c2c-0b5e4511-acff-4615-9745-6e895c692865-00%40eu-central-1.amazonses.com.

Re: [Django] #34692: django.forms.renderers.get_default_renderer()'s template loader cache is not being reset on autoloads.

[Django]

#34692: django.forms.renderers.get_default_renderer()'s template loader cache is
not being reset on autoloads.
+---
 Reporter:  Andrew  |Owner:  Priyank Panchal
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by Carlton Gibson):

 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/17106/files PR needs regression
 tests added]

-- 
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/01070189aacc5e8b-962643f2-b39a-4a60-b003-b75ffaf54591-00%40eu-central-1.amazonses.com.