#28350: UnboundLocalError in RenameField.state_forwards() when renaming
nonexistent
field
-------------------------------------+-------------------------------------
Reporter: Daniel Hahler | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
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
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"c1621d80089cb3e77c8a504310feeb24fea61afe" c1621d80]:
{{{
#!CommitTicketReference repository=""
revision="c1621d80089cb3e77c8a504310feeb24fea61afe"
[1.11.x] Fixed #28350 -- Fixed UnboundLocalError crash in RenameField with
nonexistent field.
Thanks Tim for the review.
Backport of 5cbcb3683964205ce023157ca181d05a31be2ab5 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28350#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 [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.b712e1bd2ca703760a2a8cbf5a3f211a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
