On Oct 7, 5:14 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Sed wrote:
> >> you need to easy_install with -m/--multi-version. All of your packages.
> > Unfortunately, this is not even working :(
>
> It is.
I see !!! thanks !!!
the fact is that if you have only one egg of sqlachemy module (
Sed wrote:
>> you need to easy_install with -m/--multi-version. All of your packages.
> Unfortunately, this is not even working :(
It is.
[EMAIL PROTECTED]:/tmp$ virtualenv --no-site-packages test
New python executable in test/bin/python2.5
Installing setuptoolsdone.
[EMAIL PROTECTED
> you need to easy_install with -m/--multi-version. All of your packages.
Unfortunately, this is not even working :(
let's try it:
$ easy_install -m 'SQLAlchemy==0.4.6'
...
$ easy_install -m 'SQLAlchemy==0.4.4'
...
check that the easy-install.pth doesn't contain any more some sql
entry:
$ grep -i
Sed wrote:
> Hello,
>
> I thought that with eggs, I will be able to choose at run time, which
> version of an egg I would like to use.
>
> But after some tests with dummy eggs, I've tried to make it work with
> SQLAlchemy for example, with no success at all.
>
> So does some one know if such fe
Hello,
I thought that with eggs, I will be able to choose at run time, which
version of an egg I would like to use.
But after some tests with dummy eggs, I've tried to make it work with
SQLAlchemy for example, with no success at all.
So does some one know if such feature is available with eggs ?
