[sqlalchemy] Re: Changes in SA 0.3 cause migrate 0.2 to fail

2006-10-28 Thread Evan Rosson 

> Excellent, thanks. Wasn't sure whether you were still hanging around
> on the SQLAlchemy list or not, which is why I said "Anyone want to
> tackle this?".

Yup, I'm still around, though the times at which I read the list can
be a little erratic.

Posted migrate 0.2.1 earlier today; it should work with SA 0.3.

-- 
- Evan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~--~~~~--~~--~--~---

[sqlalchemy] Re: Changes in SA 0.3 cause migrate 0.2 to fail

2006-10-25 Thread Robin Munn 

On 10/25/06, Evan Rosson <[EMAIL PROTECTED]> wrote:
>
> I noticed this myself a few days ago, after upgrading... didn't have a
> chance to fix things then, though. Thanks for the reminder.
>
> This error's gone in r216, and there's a few more things to fix before
> a new version that's happy with 0.3.

Excellent, thanks. Wasn't sure whether you were still hanging around
on the SQLAlchemy list or not, which is why I said "Anyone want to
tackle this?".

I'm going to be giving an SQLAlchemy demonstration/teaching session in
a couple weeks to about a dozen or so people I work with; it would be
nice to be able to show off migrate alongside of SQLAlchemy 0.3.

-- 
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~--~~~~--~~--~--~---

[sqlalchemy] Re: Changes in SA 0.3 cause migrate 0.2 to fail

2006-10-25 Thread Evan Rosson 

I noticed this myself a few days ago, after upgrading... didn't have a
chance to fix things then, though. Thanks for the reminder.

This error's gone in r216, and there's a few more things to fix before
a new version that's happy with 0.3.

On 10/25/06, Robin Munn <[EMAIL PROTECTED]> wrote:
>
> Looks like the migrate script (http://erosson.com/migrate/) could use
> some attention:
>
> [EMAIL PROTECTED]:~/projects/python$ migrate --help
> Traceback (most recent call last):
>   File "/usr/bin/migrate", line 5, in ?
> pkg_resources.run_script('migrate==0.2.0', 'migrate')
>   File 
> "/usr/lib/python2.4/site-packages/setuptools-0.6c3-py2.4.egg/pkg_resources.py",
> line 407, in run_script
> self.require(requires)[0].run_script(script_name, ns)
>   File 
> "/usr/lib/python2.4/site-packages/setuptools-0.6c3-py2.4.egg/pkg_resources.py",
> line 1084, in run_script
> execfile(script_filename, namespace, namespace)
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/EGG-INFO/scripts/migrate",
> line 2, in ?
> from migrate.versioning.shell import main
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/shell.py",
> line 6, in ?
> from migrate.versioning import api,exceptions
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/api.py",
> line 5, in ?
> from migrate.versioning.repository import *
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/repository.py",
> line 8, in ?
> from migrate.versioning import script,exceptions,version
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/script/__init__.py",
> line 1, in ?
> from py import *
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/script/py.py",
> line 2, in ?
> from logsql import LogsqlFile
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/script/logsql.py",
> line 2, in ?
> from migrate.versioning import logengine
>   File 
> "/usr/lib/python2.4/site-packages/migrate-0.2.0-py2.4.egg/migrate/versioning/logengine.py",
> line 200, in ?
> class LogEngine(base.ComposedSQLEngine):
> AttributeError: 'module' object has no attribute 'ComposedSQLEngine'
>
> I haven't gone through migrate's code to find out if there are any
> other places where it's breaking, and there probably are such places.
> But right now, I've got an unrelated deadline breathing down my neck,
> so I can't spare the time.
>
> Anyone want to give the migrate script some attention?
>
> --
> Robin Munn
> [EMAIL PROTECTED]
> GPG key 0xD6497014
>
> >
>


-- 
- Evan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~--~~~~--~~--~--~---

[sqlalchemy] Re: Changes in SA 0.3 cause migrate 0.2 to fail

2006-10-25 Thread Michael Bayer 

i can tell you the cause of that specific error, the
"base.ComposedSQLEngine" class is now called "base.Engine".


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~--~~~~--~~--~--~---