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.
* 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>
* Attachment "8760.diff" added.
--
Ticket URL: <https://code.djangoproject.com/ticket/8760>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:9>
* status: new => assigned
* owner: nobody => hassam
--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:10>
* owner: nobody => David Smith
* status: new => assigned
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>
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:12>
* 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>
* 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>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/8760#comment:15>
* 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>
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>