#23982: Migrations produced under Python 2 require fixing when run under Python
3
-------------------------------+--------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7
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 bmispelon):
Hi,
Isn't the problem the fact that you're using "native strings" (ie byte
strings on Python 2 but unicode strings on Python 3) for your
`verbose_name` in your models?
If you're using `verbose_name='asdf'` on Python2 and you don't have `from
__future__ import unicode_literals` at the top of your file then you are
actually using `verbose_name=b'asdf'` so the migration is correct, no?
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#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/069.fa925508686edb8fbadddb2235fda07c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
