Problem running evolution

20 views
Skip to first unread message

ActionAnton

unread,
Apr 6, 2010, 8:17:30 AM4/6/10
to Django Evolution
Hi

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

Russell Keith-Magee

unread,
Apr 12, 2010, 1:23:43 AM4/12/10
to django-e...@googlegroups.com

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 %-)

Christian Hammond

unread,
Apr 12, 2010, 2:39:41 AM4/12/10
to django-e...@googlegroups.com
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.

Short-term, I probably will be updating django-evolution for Django 1.2, as we're in no position today to be able to move to South, and will need to support Django 1.2 with our next major release.

Christian

--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com



--
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.


Russell Keith-Magee

unread,
Apr 12, 2010, 2:46:37 AM4/12/10
to django-e...@googlegroups.com
On Mon, Apr 12, 2010 at 2:39 PM, Christian Hammond <chi...@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.
>
> Short-term, I probably will be updating django-evolution for Django 1.2, as
> we're in no position today to be able to move to South, and will need to
> support Django 1.2 with our next major release.

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 %-)

Christian Hammond

unread,
Apr 12, 2010, 2:49:01 AM4/12/10
to django-e...@googlegroups.com
Fair enough :) An experiment for another day then. In the meantime, I'll look at what it takes to get it working with Django 1.2 again.


Christian

--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com



Yours,
Russ Magee %-)

Carl Meyer

unread,
Apr 12, 2010, 10:22:29 AM4/12/10
to Django Evolution
Hi Christian,

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

Christian Hammond

unread,
Apr 20, 2010, 6:23:15 PM4/20/10
to django-e...@googlegroups.com
Hi,

I never saw this issue when working on Django 1.2 support, but I'd very much like to see if things improve for you when updating Django Evolution.

If you still get that error, can you provide a full stack trace?

Thanks,


Christian

--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


--
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.

Reply all
Reply to author
Forward
0 new messages