Fix unicode issue when generating migration with py2 or py3 #359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running makemigrations on Python 3 will generate a new migration because of Query.connection.help_text which is not unicode on Python 2 which lead to a migration file with byte see explorer/migrations/0006_query_connection.py
Adding
from __future__ import unicode_literals
will solve this problem but I've to add the right migration any way so that Django will not try generate a new one using Python3.I have also added minor fixes to use
@six.python_2_unicode_compatible
I hope this will be merged and released as soon as possible.