[Buildbot-devel] can't find sqlalchemy-migrate during installation

[John Carr]

> On 30 Dec 2014, at 10:54, Pierre Tardy <tardyp at gmail.com> wrote:
> 
> 
> PEP440Warning: 'sqlalchemy (migrate-0.4.0)' is being parsed as a legacy,
> hum, that looks interesting, it is detecting  migrate-0.4.0 as the version..
> I think you may retry with pip, but before do a 'pip install -U pip', which runs a self upgrade of pip inside the virtualenv.
> 
> The rule of thumb is to always use pip which is to our experience more stable.


The pep440 working is a red herring, e.g.:

https://bitbucket.org/pypa/setuptools/issue/307/pep440-code-in-setuptools-821-is-parsing#comment-14405459 <https://bitbucket.org/pypa/setuptools/issue/307/pep440-code-in-setuptools-821-is-parsing>

But i’ve seen this in other projects - setuptools 8.0 introduces PEP440 version numbers and that change means projects that have versions like:

foo==0.1, ==0.2, ==0.3

no longer work. It appears to be intentional. The , now means AND! Downgrading setuptools to 7.0 may help if this is the problem here.

We might need to do a release with:

sqlalchemy-migrate>=0.6.1,<=0.7.2

to support new setuptools.

Cheers
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20141230/e5e915cb/attachment.html>