Changes between Version 1 and Version 2 of Ticket #23226, comment 4


Ignore:
Timestamp:
08/05/14 21:57:46 (8 years ago)
Author:
Simon Charette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23226, comment 4

    v1 v2  
    1 I guess we didn't hit this before because most of the code bases that intent to support both Python 2 and Python 3 use unicode literals (`from __future__ import unicode_literals`) which would have made the `unique_together` fields `unicode` instances on Python 2 which would have been serialized without the problematic `b` prefix.
     1I guess we didn't hit this before because most of the code bases that intent to support both Python 2 and Python 3 use unicode literals (`from __future__ import unicode_literals`) which would have made the `unique_together` fields `unicode` instances on Python 2 that would have been serialized without the problematic `b` prefix.
    22
    33Can you confirm your migration was generated on Python 2 from a model file without the `from __future__ import unicode_literals` import?
Back to Top