|Version 3 (modified by eugene@…, 10 years ago) (diff)|
Removing the magic: the cheat sheet
Work in progress.
This document assumes a basic familiarity with Removing the magic changes. It is designed to be used as a simple cheat sheet during a conversion process providing links to relevant parts Removing the magic document. It is organized by functional areas: databases, settings, models, views, templates, and template tags. This document doesn't cover new functionality.
Optional (saves time): if your project doesn't have manage.py file in the project's directory, copy it from django/conf/project_template/.
Database changes are covered extensively in Database changes you'll need to make. Just execute appropriate SQL scripts.
Optional (saves space): package column of auth_permission table is not used anymore. You can drop it by executing following SQL statement (works for MySQL):
ALTER TABLE `auth_permission` DROP COLUMN `package`;
Eugene's note: after conversion I found that my permissions are screwed up. I regenerated them this way:
- Delete a content of following tables (you can do it now):
- After you finished with code changes, run django-admin.py syncdb or manage.py syncdb. Don't do it now'''
It repopulates the content of said tables properly, but an administrator has to reassign group and user permissions again in Admin. Obviously it can be a problem, if you have hundreds of users with arcane permissions.
- If your applications still live in yourproject/apps/ directory, you can move them up one level: move yourproject/apps/yourapp/ to yourproject/yourapp.
- Relocate models by moving content of files in your yourapp/models/ directory to yourapp/models.py file.
- If your models use datetime or db modules without exporting them directly, add import statements.
- Relocate Model and Field classes: use django.db.models instead of django.core.meta.
- Convert the META.admin member to new inner class Admin of the model. Don't forget to remove all pesky commas at the end of lines.
- Remove from META following parameters: admin (see the previous step), module_name, exceptions, module_constants, and where_constraints. If now your class META is empty, delete it. Otherwise rename it to class Meta.
- Replace __repr__ with __str__.
- If you use _pre_save(), _post_save(), _pre_delete(), and/or _post_delete() hooks, replace them by overriding save() and delete() methods.
- If your model has objects attribute, rename it.
- Import your models directly the Python way. For example, if your model Person is in yourproject/yourapp/models.py file, use:
from yourproject.yourapp.models import Person
- Change import statements to reflect the namespace simplification:
- django.utils.httpwrappers => django.http
- django.core.exceptions.Http404 => django.http.Http404
- django.core.template => django.template
- django.core.formfields => django.forms
- django.core.extensions => django.shortcuts
- renamed: django.core.extensions.DjangoContext => django.template.RequestContext
- Former module settings is an instance now. Import it using from django.cong import settings.
- Include template extensions explicitly.
- Convert to new Database API. Warning: usually this is the most time-consuming step. Be careful''
- Rename DoesNotExist exception: people.PersonDoesNotExist becomes Person.DoesNotExist.
- If you use get_object_or_404() and get_list_or_404(), change their parameters. Note: you cannot use field__ne and order_by keywords. Use exclude() and order_by() methods of new Database API.
- If you use Django's authentication, update your code to reflect the consolidation.
- If you use manipulators, update your code: django.core.formfields is django.forms now.
Settings and URLs
If you decided to regenerate permissions, now is the good time to execute django-admin.py syncdb or manage.py syncdb. Remember that an administrator should reassign permissions to all users using Admin.