Hello, Just noticed, if you generate Django 1.7 migrations using Python 2, they won't be Python 3 compatible.
i.e. strings such as 'name' will become b'name' in the migration, which doesn't work in python 3. The work around seems to be to remove the b'...' by hand or make the migrations using Python 3. Presumably if you use unicode strings everywhere or add the following to the top of model files, this wouldn't be an issue. Not tested it myself. from __future__ import unicode_literals I reported this upstream: https://code.djangoproject.com/ticket/23455 Thanks -- Brian May <br...@microcomaustralia.com.au>
