#25906: `squashmigrations` generates migrations that don't work with Python 3
----------------------------+--------------------
Reporter: patrys | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
When I run `squashmigrations` I get something similar to the following:
{{{
class Migration(migrations.Migration):
replaces = [(b'registration', '0001_initial'), (b'registration',
'0002_auto_20151203_1158')]
...
}}}
Notice how app names are passed as `bytes` instances.
Now in Python 3 a `bytes` objects is never equal to its Unicode (`str`)
representation. This inequality makes Django consider the squashed
migration conflicting with the migrations it replaces.
--
Ticket URL: <https://code.djangoproject.com/ticket/25906>
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/049.f4f0283e5e8017762a2d9e9f112d5d61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
