#23439: ./manage.py makemigrations fail on 3.4.1 but works on 2.7.6
-------------------------------------+-------------------------------------
Reporter: DanGamble89 | Owner: nobody
Type: Bug | Status: new
Component: Python 3 | Version: 1.7
Severity: Normal | Resolution:
Keywords: manage.py | Triage Stage:
migrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by DanGamble89):
Hey it did seem like it created a duplicate migration or it tried running
a migration that was already ran. Not sure why the 2.7.6 version didn't
seem to spit up any errors. I guess this is 'sorted' per-se as it seemed
like i was trying to do something it already had done!
Replying to [comment:2 bmispelon]:
> Looking at where the error is triggered, it seems that you've defined a
`related_name` as a bytestring somewhere in your code.
>
> Could you show your model definitions?
>
> Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/23439#comment:3>
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/069.37b0b09d01b29613ad57130c05b5a48f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
