it doesn’t look like pystache will build on python...
# development
w
it doesn’t look like pystache will build on python 3.6 any longer, which is stymying my attempts to release from 1.30.x.
…oh. hm. maybe it’s setuptools instead.
i repro locally, and things work with python3.7 or greater, but not python3.6.
f
would there be any issue with using py37 on 1.30.x?
h
A pinned version doesn't build?
w
yea. `pystache==0.5.4`… but the:
Copy code
error in pystache setup command: use_2to3 is invalid.
…error is apparently related to the setuptools version that is in use.
we’re using a python3.6 there, supplied by pyenv (“/pyenv-docker-build/versions/3.6.12”)… i think that
setuptools
would be provided by the interpreter…?
will look at whether our 3.6 version floated.
…oh. perhaps that docker image was upgraded, and we’re not pinned to the older image.
does https://hub.docker.com/r/pantsbuild/centos7/tags mean that we don’t have an older release available?
…yikes. yea, they’ve all been garbage collected.
Copy code
$ docker image history pantsbuild/centos7
IMAGE          CREATED         CREATED BY                                      SIZE      COMMENT
21aefba52756   13 months ago   /bin/sh -c #(nop)  ENTRYPOINT ["/usr/bin/scl…   0B
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   48B
<missing>      13 months ago   /bin/sh -c #(nop)  ENV PATH=/aws-docker-buil…   0B
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   107MB
<missing>      13 months ago   /bin/sh -c #(nop)  ENV AWS_CLI_ROOT=/aws-doc…   0B
<missing>      13 months ago   /bin/sh -c #(nop)  ENV PATH=/pyenv-docker-bu…   0B
<missing>      13 months ago   /bin/sh -c #(nop)  ENV PATH=/pyenv-docker-bu…   0B
<missing>      13 months ago   /bin/sh -c #(nop)  ENV PATH=/pyenv-docker-bu…   0B
<missing>      13 months ago   /bin/sh -c #(nop)  ENV PATH=/pyenv-docker-bu…   0B
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   219MB
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   196MB
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   181MB
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   129MB
<missing>      13 months ago   |4 PYTHON_27_VERSION=2.7.18 PYTHON_36_VERSIO…   7.06MB
<snip>
well… maybe i try upgrading the deps instead.
pystache is ancient, so that’s out.
will try building the centos7 image locally and then using it inline (since we’re already building the travis image, apparently)
@hundreds-father-404: can you think of anything that is still using the
pantsbuild/centos7
image, other than the 1.30.x branch? i’m re-building the image locally in the travis job, but if that works, i might re-publish an older tag if only 1.30.x is using it
h
Did we stop using it for 2.0?
w
…apparently not. were still using it as of the most recent 2.0.x release. good to know.
it looks like it’s not specific to the python version anyway. it’s only setuptools that floated.
ok, yea: that did it. pheew.
❤️ 1
for future reference, apparently setuptools can float in a virtualenv? this was the same python version, and the requirements.txt specifies an explicit version… but we floated up a few versions to
58.*
https://github.com/pantsbuild/pants/pull/13143/commits/8e4c6285fe6d7775796eb1248a7ac4b560f40e80
👍 1
😬 1
i guess that the virtualenv creation must dynamically resolve setuptools or something
h
Ooof
Bitrot is rough
Frustrating, thanks for toughing it out