edan_f0

Verlauf

Maik Hoepfel 7dcecdcb97 Use Python 3 to create native migrations Native migrations created with Python 2 differ from ones created with Python 3. More importantly, they failed when used in Python 3, but not vice versa. This is caused by field names being marked as byte strings when using Python 2. This rewrites the native migrations, which probably isn't a bad thing either, because they were created with a pre-RC2 version of Django, and Django 1.7 has since seen a few more migration-related fixes. It's likely Django now does the correct thing and generates Python 2 and 3 compatible migrations under both versions of Python.		vor 11 Jahren
..
migrations	Use Python 3 to create native migrations	vor 11 Jahren
south_migrations	Move migrations into south_migrations directory	vor 11 Jahren
__init__.py	Implement AppConfig objects for non-dashboard apps	vor 11 Jahren
abstract_models.py	Test and handle text representations of models	vor 11 Jahren
admin.py	Make countries searchable in Django admin	vor 12 Jahren
config.py	flake8: ignore new migrations directories and fix warnings	vor 11 Jahren
forms.py	Add test runner for demo site	vor 12 Jahren
models.py	Rename model_registered to is_model_registered	vor 11 Jahren