Closed escapewindow closed 5 years ago
Hmm, this is weird... I usually use docker to run tox test, something like this:
docker run -ti -v $PWD:/src python:3.6 /bin/bash
apt update
apt install apt-get install zipalign openjdk-8-jdk-headless
pip install tox
cd /src
tox -e py36
The same for py37.
It's scriptworker==23.0.7
here. Maybe try to kill the .tox
directory? I'm not sure if tox is smart enough to detect a newer version of scriptworker if it's already installed and the version is not explicit (like in the base.in
file).
I vaguely remember that tox treats differently explicitly listed packages in the deps
section and the ones coming from a file using -r
, as I changed in that PR.
I think since 632919f237d6de0dcbab2f6f524a09f1c39d7d61 .
e.g.
First, why am I installing scriptworker==0.6.0? Second, why can't I find the scriptworker module?
@rail is tox working for you locally?