On Tue, Mar 15, 2011 at 3:18 PM, Nate Coraor <nate@bx.psu.edu> wrote:
Peter Cock wrote:
$ sh manage_db.sh upgrade Traceback (most recent call last): File "./scripts/manage_db.py", line 12, in <module> from migrate.versioning.shell import main ImportError: No module named migrate.versioning.shell
This is a bug, but as a workaround try the following:
python -ES ./scripts/manage_db.py upgrade
Hi Nate, The workaround failed for me, $ python -ES ./scripts/manage_db.py upgrade Traceback (most recent call last): File "./scripts/manage_db.py", line 12, in <module> from migrate.versioning.shell import main File "/Users/pjcock/repositories/galaxy-central-stuck-db-75/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/shell.py", line 7, in <module> from migrate.versioning.base import * File "/Users/pjcock/repositories/galaxy-central-stuck-db-75/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/base/__init__.py", line 5, in <module> from const import databases,operations File "/Users/pjcock/repositories/galaxy-central-stuck-db-75/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/base/const.py", line 7, in <module> from sqlalchemy.util import OrderedDict ImportError: No module named sqlalchemy.util There's probably some PYTHONPATH or something solution to this... I don't use eggs enough to see it immediately though. Is there a bug open for the upgrade issue? Thanks, Peter