I thought these rough notes might be useful to anyone migrating from Django 1.4 (and possibly 1.3) to Django 1.11.<\/p>\n
Remove \u2018south\u2019 from your INSTALLED_APPS<\/p>\n
Remove all app\/migrations files except for __initi__.py . Remove any *.py[c|o] files.<\/p>\n
Make sure there\u2019s no migrations specific code in your app\/migrations\/__init__.py files<\/p>\n
https:\/\/docs.djangoproject.com\/en\/1.7\/topics\/migrations\/<\/a><\/p>\n This is a 1.3 app migrated to 1.4 and now is being migrated to 1.11.<\/p>\n Will probably need a new manage.py file. Create a dummy project and copy manage.py over your existing manage.py file or diff the two). Rename your settings directory to match the name of your project. In my case the project is portal, settings renamed to portal.<\/p>\n django.conf.urls.defaults is replaced by <\/span>django.conf.urls<\/p>\n patterns() is gone, see:<\/p>\n https:\/\/docs.djangoproject.com\/en\/1.11\/releases\/1.8\/#django-conf-urls-patterns<\/a><\/p>\n django.views.generic.simple is gone, removed in 1.5.<\/p>\n Replace django.views.generic.simple.direct_to_template with TemplateView:<\/p>\n Replaced with:<\/p>\n django.contrib.databrowse is gone. See:<\/p>\n This error:<\/p>\n Change in Django 1.8. See:<\/p>\n Quick fix is:<\/p>\n But you will need to confirm that you want the form to expose all fields.<\/p>\n Removal of django.contrib.formtools:<\/p>\n Is now separate package, install with pip:<\/p>\n Change imports from django.contrib.formtools to formtools. For example:<\/p>\n Becomes:<\/p>\n model._meta.get_all_field_names() is gone.<\/p>\n See:<\/p>\n https:\/\/docs.djangoproject.com\/en\/1.9\/ref\/models\/meta\/#migrating-from-the-old-api<\/a><\/p>\n This is verbatim from the docs:<\/p>\n This provides a 100% backwards compatible replacement, ensuring that both field names and attribute names\u00a0 While this isn\u2019t 100% backwards compatible, it may be sufficient in many situations.<\/p>\n BaseCommand.option_list is gone.<\/p>\n See https:\/\/docs.djangoproject.com\/en\/1.11\/releases\/1.8\/#extending-management-command-arguments-through-command-option-list<\/a> .<\/p>\n See here for how to add arguments:<\/p>\n https:\/\/docs.djangoproject.com\/en\/1.11\/howto\/custom-management-commands\/#accepting-optional-arguments<\/a><\/p>\n These custom options can be added in the add_arguments()<\/b><\/a> method like this:<\/span><\/p>\n class<\/b><\/span> Command<\/b><\/span>(BaseCommand):<\/span><\/p>\n \u00a0 \u00a0 <\/span><\/span>def<\/b><\/span> add_arguments<\/span>(<\/span>self<\/span>, parser):<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 <\/span><\/span># Positional arguments<\/i><\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 <\/span>parser<\/span>.<\/span>add_argument(<\/span>‘poll_id’<\/span>, nargs<\/span>=<\/span>‘+’<\/span>, <\/span>type<\/span>=<\/span>int<\/span>)<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 <\/span><\/span># Named (optional) arguments<\/i><\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 <\/span>parser<\/span>.<\/span>add_argument(<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <\/span><\/span>‘–delete’<\/span>,<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <\/span>action<\/span>=<\/span>‘store_true’<\/span>,<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <\/span>dest<\/span>=<\/span>‘delete’<\/span>,<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <\/span>default<\/span>=<\/span>False<\/b><\/span>,<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <\/span>help<\/span>=<\/span>‘Delete poll instead of closing it’<\/span>,<\/span><\/p>\n \u00a0 \u00a0 \u00a0 \u00a0 <\/span>)<\/span><\/p>\n Bigger or more complex databases may want to do a manual migration where the database is migration using django models.<\/p>\n https:\/\/www.calazan.com\/migrating-django-app-from-mysql-to-postgresql\/<\/a><\/p>\n I’ll update this as I have time.<\/p>\n","protected":false},"excerpt":{"rendered":" I thought these rough notes might be useful to anyone migrating from Django 1.4 (and possibly 1.3) to Django 1.11. Moving from South to Django Migrations 1. Update your settings files: Remove \u2018south\u2019 from your INSTALLED_APPS 2. Remove migrations. Remove all app\/migrations files except for __initi__.py . Remove any *.py[c|o] files. Make sure there\u2019s no … Continue reading Migrate Django 1.4 to 1.11<\/span> 3. Run new Migrations<\/h3>\n
python manage.py makemigrations;\r\n\r\npython manage.py migrate;<\/pre>\n
Moving from Django 1.3\/1.4 -> 1.11<\/b><\/h1>\n
URLS files:<\/b><\/h3>\n
Views<\/h3>\n
django.views.generic.simple<\/h4>\n
from<\/span> django.views.generic import<\/span> TemplateView\r\n<\/span><\/pre>\nShortcuts<\/b><\/h3>\n
from<\/span> django.shortcuts import<\/span> RequestContext<\/span><\/pre>\nfrom<\/span> django.template import<\/span> RequestContext<\/span><\/pre>\nContrib<\/h3>\n
\n
Forms<\/b><\/h3>\n
django.core.exceptions.ImproperlyConfigured: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is prohibited; form BlahForm needs updating.<\/pre>\n
\n
fields = '__all__'<\/span><\/pre>\nFormtools<\/h4>\n
pip install django-formtools<\/pre>\n
from<\/span> django.contrib.formtools.preview import<\/span> FormPreview<\/span><\/pre>\nfrom<\/span> formtools.preview import<\/span> FormPreview<\/span><\/pre>\nModels<\/b><\/h3>\n
MyModel._meta.get_all_field_names()<\/span><\/code>\u00a0becomes<\/em>:<\/p>\nfrom<\/span> itertools<\/span> import<\/span> chain<\/span>\r\nlist<\/span>(<\/span>set<\/span>(<\/span>chain<\/span>.<\/span>from_iterable<\/span>(<\/span>\r\n (<\/span>field<\/span>.<\/span>name<\/span>,<\/span> field<\/span>.<\/span>attname<\/span>)<\/span> if<\/span> hasattr<\/span>(<\/span>field<\/span>,<\/span> 'attname'<\/span>)<\/span> else<\/span> (<\/span>field<\/span>.<\/span>name<\/span>,)<\/span>\r\n for<\/span> field<\/span> in<\/span> MyModel<\/span>.<\/span>_meta<\/span>.<\/span>get_fields<\/span>()<\/span>\r\n # For complete backwards compatibility, you may want to exclude<\/span>\r\n # GenericForeignKey from the results.<\/span>\r\n if<\/span> not<\/span> (<\/span>field<\/span>.<\/span>many_to_one<\/span> and<\/span> field<\/span>.<\/span>related_model<\/span> is<\/span> None<\/span>)<\/span>\r\n)))<\/span>\r\n<\/pre>\n<\/div>\n<\/div>\nForeignKey<\/span><\/code>s are included, but fields associated with\u00a0GenericForeignKey<\/span><\/code>s are not. A simpler version would be:<\/p>\n[<\/span>f<\/span>.<\/span>name<\/span> for<\/span> f<\/span> in<\/span> MyModel<\/span>.<\/span>_meta<\/span>.<\/span>get_fields<\/span>()]<\/span>\r\n<\/pre>\n<\/div>\n<\/div>\nCommands<\/b><\/h3>\n
BaseCommand<\/h4>\n
Arguments<\/h4>\n
Move from MySQL to Postgres<\/b><\/h2>\n