#32893: Missing import statement in generated migration (NameError: name
'models'
is not defined)
-------------------------------------+-------------------------------------
Reporter: Jaap Joris Vens | Owner: Abhyudai
Type: Bug | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: fixed
Keywords: migrations writer | Triage Stage: Ready for
missing import | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fde6fb28984a76d5bee794f4c0458eb25fe56fcd" fde6fb2]:
{{{
#!CommitTicketReference repository=""
revision="fde6fb28984a76d5bee794f4c0458eb25fe56fcd"
Fixed #32893 -- Fixed serialization of models.Model class in migrations.
Migrations assumed that an import of the models.Model class must
already be included when it's serialized, but for models with only
custom fields this was not necessarily the case.
Thanks Jaap Joris Vens for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32893#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.0a0b916c15c5de7d411b7430347bceba%40djangoproject.com.
