#27114: Migrations: AttributeError: can't set attribute
-------------------------------------+-------------------------------------
Reporter: sweaver360 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: AttributeError | Triage Stage:
Migrations 1.10 | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by sweaver360):
Replying to [comment:1 timgraham]:
> Can you provide a minimal project that reproduces the issue? We can't do
much to diagnose the issue based on the stacktrace alone.
I'm guessing it won't happen if I just start a new Django 1.10 project
since no one else is reporting the issue, which makes me think it's
probably something in my project. Is there any way to find out which
migration is causing the exception? It's hard to tell what's going on
with it only referencing core Django files in the stack trace.
--
Ticket URL: <https://code.djangoproject.com/ticket/27114#comment:2>
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.d749bdda8920ded7b68530844401072c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
