Re: [Django] #35035: BaseFormSet should use Form's default_renderer before defaulting to get_default_renderer().

16 views
Skip to first unread message

Django

unread,
Dec 14, 2023, 2:39:22 AM12/14/23
to django-...@googlegroups.com
#35035: BaseFormSet should use Form's default_renderer before defaulting to
get_default_renderer().
-------------------------------------+-------------------------------------
Reporter: Christophe Henry | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Forms | Version: 4.2
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
-------------------------------------+-------------------------------------

Comment (by Christophe Henry):

Ok. Thank you for the information. I now realize that I tried to fix
something that was already fixed in Django 5.0. Would it be possible to
backport this fix to Django 4.2? Do I need to open a new ticket for this?

--
Ticket URL: <https://code.djangoproject.com/ticket/35035#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Dec 14, 2023, 2:46:18 AM12/14/23
to django-...@googlegroups.com
#35035: BaseFormSet should use Form's default_renderer before defaulting to
get_default_renderer().
-------------------------------------+-------------------------------------
Reporter: Christophe Henry | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Forms | Version: 4.2
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
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak):

Replying to [comment:2 Christophe Henry]:
> []Ok. Thank you for the information. I now realize that I tried to fix


something that was already fixed in Django 5.0. Would it be possible to
backport

[https://github.com/django/django/commit/95e4d6b81312fdd9f8ebf3385be1c1331168b5cf
this fix (95e4d6b)] to Django 4.2? Do I need to open a new ticket for
this?[]

Django 4.2 is in extended support and it doesn't receive bugfixes anymore
(except security patches).

--
Ticket URL: <https://code.djangoproject.com/ticket/35035#comment:3>

Reply all
Reply to author
Forward
0 new messages