I'm using evolution with python 2.6 and django 1.2.0 beta 1
When doing syncdb I get the following error message:
AttributeError: 'module' object has no attribute 'EvolutionOperations'
Is there a way around this problem?
-Anton
Django Evolution hasn't been updated to work with Django 1.2. Unless
someone else steps up to do the work, I don't think Django 1.2 support
will ever be added. I expect to make a formal announcement regarding
the future of Django Evolution in the near future.
If you have a need need a schema migration framework, I suggest
checking out South.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups "Django Evolution" group.
To post to this group, send email to django-e...@googlegroups.com.
To unsubscribe from this group, send email to django-evoluti...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-evolution?hl=en.
No, I haven't given any thought to migration paths. I don't currently
have any code in production that is using Evolution, so you would be a
in a much better place to comment on this than I.
Yours,
Russ Magee %-)
Yours,
Russ Magee %-)
On Apr 12, 2:39 am, Christian Hammond <chip...@chipx86.com> wrote:
> Is there any sort of migration path for installs using django-evolution to
> migrate to South? Unfortunately, we have several hundred installs of Review
> Board in production world-wide that will need an easy, automated migration
> path if we do decide to support South.
I've migrated a couple production sites from Evolution to South. In my
experience it wasn't actually that hard; just add South to
INSTALLED_APPS, stop adding evolutions, and start adding migrations
instead. Once a given installation has run all of its evolutions, you
can simply remove all evolutions/ directories and remove Evolution
from INSTALLED_APPS. So in the worst case (for someone running a
version prior to the latest evolution who wants to upgrade to a post-
transition release) it's a two-step process: upgrade to a release with
the latest evolution, run evolve, then upgrade to a post-evolutions
release.
I haven't attempted to do an Evolution->South migration that preserved
evolution history as migrations for the long run; just didn't seem
worth it.
Carl
--
You received this message because you are subscribed to the Google Groups "Django Evolution" group.
To post to this group, send email to django-e...@googlegroups.com.
To unsubscribe from this group, send email to django-evoluti...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-evolution?hl=en.