Re: [Django] #8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message key

16 views
Skip to first unread message

Django

unread,
Jun 5, 2015, 6:29:04 AM6/5/15
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
--------------------------------------+------------------------------------
Reporter: durdinator | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by giuliettamasina):

Should this change happen? The comments are ambiguous :)

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

Django

unread,
Jun 5, 2015, 11:37:49 AM6/5/15
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
--------------------------------------+------------------------------------
Reporter: durdinator | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):

* has_patch: 0 => 1


Comment:

The implementation isn't difficult (see attached patch). The question is
whether or not we accept this as a backwards incompatible change (to be
documented if so) or try for some deprecation path. I'm not sure how a
deprecation would work.

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:8>

Django

unread,
Jun 5, 2015, 11:38:00 AM6/5/15
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
--------------------------------------+------------------------------------
Reporter: durdinator | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):

* Attachment "8760.diff" added.


--
Ticket URL: <https://code.djangoproject.com/ticket/8760>

Django

unread,
Jun 30, 2015, 10:37:19 AM6/30/15
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
--------------------------------------+------------------------------------
Reporter: durdinator | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):

* needs_better_patch: 0 => 1


--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:9>

Django

unread,
Feb 21, 2017, 2:14:52 AM2/21/17
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
--------------------------------------+------------------------------------
Reporter: durdinator | Owner: hassam
Type: Cleanup/optimization | Status: assigned

Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by hassam):

* status: new => assigned
* owner: nobody => hassam


--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:10>

Django

unread,
Mar 5, 2020, 3:51:18 PM3/5/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith

Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Smith):

* owner: nobody => David Smith


* status: new => assigned

Django

unread,
Mar 5, 2020, 5:36:42 PM3/5/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by David Smith):

I've created a pull request with the patch that Tim provided. Making this
change only broke one test and I've provided a fix for this.

Hopefully this can help aid a decision on if we should make this change.
If we should then is it 'ok' as a breaking change or do we need to try for
a deprecation path.

From just the notes above it seems like a trivial inconsistency and not
one that anyone is particularly passionate about given how long the ticket
has been open. Therefore if it's going to cause any issues for anyone
maybe it's just best to not fix and close the ticket?

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:11>

Django

unread,
Mar 5, 2020, 5:40:23 PM3/5/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | 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: <https://code.djangoproject.com/ticket/8760#comment:12>

Django

unread,
Mar 10, 2020, 10:05:44 AM3/10/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):

* needs_better_patch: 0 => 1

* needs_tests: 0 => 1
* needs_docs: 0 => 1


Comment:

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

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:13>

Django

unread,
Mar 11, 2020, 5:30:11 PM3/11/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | 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

* needs_tests: 1 => 0
* needs_docs: 1 => 0


Comment:

I've now added a deprecation warning, docs and tests to this PR. So ready
for next review.

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:14>

Django

unread,
Mar 12, 2020, 4:42:18 AM3/12/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: forms | 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 felixxm):

* stage: Accepted => Ready for checkin


--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:15>

Django

unread,
Mar 12, 2020, 5:24:32 AM3/12/20
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed

Keywords: forms | 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 <felisiak.mariusz@…>):

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


Comment:

In [changeset:"ccf32aca442feae4c765fb6133c418b4e387f428" ccf32ac]:
{{{
#!CommitTicketReference repository=""
revision="ccf32aca442feae4c765fb6133c418b4e387f428"
Fixed #8760 -- Changed ModelMultipleChoiceField to use invalid_list as a
error message key.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:16>

Django

unread,
Jan 14, 2021, 2:12:18 PM1/14/21
to django-...@googlegroups.com
#8760: forms.ModelMultipleChoiceField should use "invalid_list" as error message
key
-------------------------------------+-------------------------------------
Reporter: durdinator | Owner: David
Type: | Smith
Cleanup/optimization | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed
Keywords: forms | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

In [changeset:"bf770cc825f1af294b3b2853b39b5b161b6a056f" bf770cc8]:
{{{
#!CommitTicketReference repository=""
revision="bf770cc825f1af294b3b2853b39b5b161b6a056f"
Refs #8760 -- Removed "list" message for ModelMultipleChoiceField per
deprecation timeline.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:17>

Reply all
Reply to author
Forward
0 new messages