[llvm-dev] Test-suite bots red because of missing import
Chris Matthews via llvm-dev
llvm-dev at lists.llvm.org
Sat Jun 3 10:52:35 PDT 2017
We have both back and forward incompatibilities, so == is best.
I tried updating a bunch of these a while back. I was able to update a bunch no problem.
For packages we depend on transitively, I think just listing the package with no qualifier is fine. For our core packages (Flask, SQLAlchemy, Jinja, setuptools), we’ll probably have to make an effort to keep up to date.
> On Jun 1, 2017, at 4:24 AM, Renato Golin <renato.golin at linaro.org> wrote:
> On 1 June 2017 at 12:18, Leandro Nunes via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> So, in the end looks like this setuptools 36 was deleted from pypi. There is an issue  open on setuptools.
> This happens every so often. We shouldn't be relying on specific
> versions, but probably in ranges.
>> We can still try to make a few changes on buildbot jobs to make the scripts less reliant on the latest from pypi.
> We moved to specific versions because this didn't work, as it would
> break assumptions.
> What we need to to have ">=" and "<=" instead of "==" or latest.
> Adding Chris who may know of the right fix for those cases.
More information about the llvm-dev