#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 brian):
Replying to [comment:3 timgraham]:
It seems unfortunate that this means altering the previously working
source code, however I very much agree with your reasoning.
I would suggest that assertions be added to ensure that certain fields,
e.g. 'related_name' are always unicode strings (u"" for Python2/3 or ""
for Python3). i.e. ensure that broken code breaks for Python 2 as well as
Python 3, and possibly with a more consistent and friendly message.
Obviously this would break code that appears to be fine under Python 2.
--
Ticket URL: <https://code.djangoproject.com/ticket/23455#comment:5>
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.0b2549dbc82ed03496987068807f709b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
