#29590: get_or_create and update_or_create should not have defaults as an
optional
parameter
-------------------------------------+-------------------------------------
Reporter: Álex Córcoles | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution:
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 Álex Córcoles):
I think this is in line with changes such as:
https://docs.djangoproject.com/en/2.0/releases/2.0/#form-fields-no-longer-
accept-optional-arguments-as-positional-arguments
, where breaking changes are introduced to improve ergonomics. I am not
aware of the criteria required to accept them (I didn't see much at
https://code.djangoproject.com/ticket/28192 ), however I think this also
fits well "explicit is better than implicit".
--
Ticket URL: <https://code.djangoproject.com/ticket/29590#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.a08278fc90b8f354211776962c94a0fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
