#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 | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
It's another case of #24949 (we could coerce the `app_name` bytestring),
but an alternative is to add `from __future__ import unicode_literals` to
the `apps.py` in the project template as we do for other files. I think
the latter solution could be backported to 1.9. Should we create a
separate ticket for that and close this as a duplicate of #24949?
--
Ticket URL: <https://code.djangoproject.com/ticket/25906#comment:1>
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/064.2e5eb9aa5f58d029eb5a6616419ea256%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
