#23455: migrations created with python2 break with python3
---------------------------------+------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by timgraham):
I don't think it's a good idea to coerce field options. For example, you
might have `models.BinaryField(default=b"")`. How about instead
documenting this issue and recommending adding `unicode_literals` as
appropriate. For example, I did this for `contrib/contenttypes/models.py`
when adding migrations there in eb8600a65673649ea15ed18d17127f741807ac8b.
--
Ticket URL: <https://code.djangoproject.com/ticket/23455#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/063.c081cb8b5f86d30ac4d4e93bd6fe7d0b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
