#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE
----------------------------------+--------------------------------------
Reporter: Willem Van Onsem | Owner: nobody
Type: Uncategorized | Status: closed
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
----------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* resolution: needsinfo => wontfix
Comment:
> Yes, ...
Great, so it works as documented. That's why we have `blank`.
> ... but that seems counterintuitive
We had this debate so many times, we cannot change the long standing
behavior for an edge case of blank primary keys. TBH, I don't find it
misleading that you have to set `blank=True` to allow for blank foreign
keys.
You can start a discussion on DevelopersMailingList if you don't agree,
however, I don't think there would be consensus to change the current
behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/34635#comment:4>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018890002da6-8a6559c0-1dca-4217-a6f2-5370993d95e3-000000%40eu-central-1.amazonses.com.
