#21758: Document South->built-in migrations transition
--------------------------------------+------------------------
Reporter: kmtracey | Owner:
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+------------------------
Neither the 1.7 release notes nor
https://docs.djangoproject.com/en/dev/topics/migrations/ says anything
about how someone who has a project currently using south for schema
migrations would transition to using the built-in Migrations of 1.7.
I assumed you could upgrade to 1.7 yet continue with existing south until
you were ready to make the switch, at which point you'd essentially drop
all the history you have with south and switch over to the new way going
forward. Is that the plan?
However existing south doesn't work with current master, due to:
{{{
(django17-test) kmtracey@caktus006 16:42:54: ~/projects/playground
--> ./manage.py migrate --list
Traceback (most recent call last):
File "./manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/home/kmtracey/django/git-
django/django/core/management/__init__.py", line 426, in
execute_from_command_line
utility.execute()
File "/home/kmtracey/django/git-
django/django/core/management/__init__.py", line 418, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/kmtracey/django/git-
django/django/core/management/__init__.py", line 290, in fetch_command
klass = load_command_class(app_name, subcommand)
File "/home/kmtracey/django/git-
django/django/core/management/__init__.py", line 81, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name, name))
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
import_module
__import__(name)
File "/home/kmtracey/.virtualenvs/django17-test/local/lib/python2.7
/site-packages/south/management/commands/__init__.py", line 12, in
<module>
from south.hacks import hacks
File "/home/kmtracey/.virtualenvs/django17-test/local/lib/python2.7
/site-packages/south/hacks/__init__.py", line 8, in <module>
from south.hacks.django_1_0 import Hacks
File "/home/kmtracey/.virtualenvs/django17-test/local/lib/python2.7
/site-packages/south/hacks/django_1_0.py", line 8, in <module>
from django.db.models.loading import cache
ImportError: cannot import name cache
}}}
That strikes me as a problem introduced by the app-loading refactor...but
due to lack of doc on how people who use south are supposed to move up to
1.7 I don't know if that's a problem that should be fixed in a release of
south before 1.7 goes out or not. The first thing that's needed is some
doc on how people are supposed to make this transition.
--
Ticket URL: <https://code.djangoproject.com/ticket/21758>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.ab7bada9f3d47f7e189ebb7b1eb36cd5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
