#35554: Model.save() positional argument parsing slightly incorrect
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
| Johnson
Type: Bug | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | 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 GitHub <noreply@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"28522c3c8d5eb581347aececc3ac61c134528114" 28522c3]:
{{{#!CommitTicketReference repository=""
revision="28522c3c8d5eb581347aececc3ac61c134528114"
Fixed #35554, Refs #35060 -- Corrected deprecated *args parsing in
Model.save()/asave().
The transitional logic added to deprecate the usage of *args for
Model.save()/asave() introduced two issues that this branch fixes:
* Passing extra positional arguments no longer raised TypeError.
* Passing a positional but empty update_fields would save all fields.
Co-authored-by: Natalia <124304+ness...@users.noreply.github.com>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35554#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190502b587a-e957beab-b514-4b92-be53-138ceaf53d69-000000%40eu-central-1.amazonses.com.
