#29290: Previously squashed migration fails under Python 3 with "multiple leaf
nodes" error
----------------------------+--------------------------------------
Reporter: Ed Morley | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by Ed Morley):
Agreed.
Perhaps the best fix would be to update
[https://docs.djangoproject.com/en/1.11/topics/migrations/#supporting-
python-2-and-3 this page] to recommend manually removing the bytestring
attributes in existing migrations (after adding `from __future__ import
unicode_literals` everywhere) rather than running `makemigrations`?
--
Ticket URL: <https://code.djangoproject.com/ticket/29290#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/066.aadfe22663f2073961a039371b783bc2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
