#25906: `squashmigrations` generates migrations that don't work with Python 3
----------------------------+--------------------------------------
Reporter: patrys | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: duplicate
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):
* status: new => closed
* resolution: => duplicate
Comment:
We have the same problem (bytes/unicode discrepancy) in other places since
Django 1.7 and another solution has been proposed in #24949 so I'll add a
note about this there and mark this as a duplicate. We don't know whether
or not a user intends migrations to work on both Python 2 and 3, so
starting to throw errors when it's not really an error could be annoying.
If you disagree with the solution proposed in #24949, could you leave a
comment there?
I created #25909 for the `unicode_literals` proposal.
Thanks for raising the issue!
--
Ticket URL: <https://code.djangoproject.com/ticket/25906#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 [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.548adf7fa9069acae050bc6c7d0817e6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
