#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 hugotacito):
Personally I'm having problems when I do automated code analysis with
pylint. I know this can be solved just ignoring the migrations folder but
it would be nice if django only do this import when necessary on auto
generated migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/24514#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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.b120f5e714b4758e9a61a3fcb8b52752%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
