#24514: Unused import on some auto generated migrations
-------------------------------------+-------------------------------------
Reporter: hugotacito | Owner: chrisjluc
Type: | Status: assigned
Cleanup/optimization |
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: unused import | Triage Stage: Accepted
migrations |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by chrisjluc):
I think having `models` in a migration that doesn't use the import might
spark confusion for why it's being imported in the first place. I think it
makes the migrations cleaner by not having unused imports. I don't see
many situations where someone would manually need the `models` import.
But, in the rare occasion that they do need it, manually adding it is not
that bad. @MarkusH
--
Ticket URL: <https://code.djangoproject.com/ticket/24514#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/068.e6458e1e54b2b82cf4c96be95488ac9b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
