At 01:18 PM 4/29/2008 -0500, [EMAIL PROTECTED] wrote:
Thanks. Worked like a charm. I'll have to check out --multi-version. I've
never used it before. Is there any downside to using it?
The only downside is that you won't be able to "import sqlalchemy" at
all, without first importing pkg_re
>> Thanks, however that raises a VersionConflict exception:
Alexander> Ah. Yes. I install everything --multi-version so I have
Alexander> forgotten about this issue with the default working
Alexander> set. Maybe
Alexander> __requires__ = ['SQLAlchemy==0.4.5']
Alexander> im
On Tue, Apr 29, 2008 at 11:42 AM, <[EMAIL PROTECTED]> wrote:
>
> Alexander> The quick hack to request a version, good to use in the
> Alexander> interpreter or a "throw-away" script:
>
> Alexander> import pkg_resources
> Alexander> pkg_resources.require('SQLAlchemy==0.4.5')
> A
Alexander> The quick hack to request a version, good to use in the
Alexander> interpreter or a "throw-away" script:
Alexander> import pkg_resources
Alexander> pkg_resources.require('SQLAlchemy==0.4.5')
Alexander> import sqlalchemy
Alexander> This works when the directory
The quick hack to request a version, good to use in the interpreter or
a "throw-away" script:
import pkg_resources
pkg_resources.require('SQLAlchemy==0.4.5')
import sqlalchemy
This works when the directory that SQLAlchemy-0.4.5-py2.4.egg is in is
listed in sys.path.
On Tue, Apr 29, 2008 at 11:11
We have SQLAlchemy 0.3.3 installed via setuptools. I upgraded to 0.4.5
today but had to back that out (by editing easy-install.pth) because of API
changes. Now I have these two installs
.../site-packages/SQLAlchemy-0.3.3-py2.4.egg
.../site-packages/SQLAlchemy-0.4.5-py2.4.egg
Is there a
