Conversation
| build: | ||
| runs-on: ubuntu-latest | ||
| container: | ||
| image: python:2.7.18-buster |
There was a problem hiding this comment.
This did not work unfortunately, when I tried it.
There was a problem hiding this comment.
Oh sorry, I didn't realize you had tried this already.
There was a problem hiding this comment.
I tried it right before the other CL i mentioned you in. It didn't work because other parts of the cloud tool chain needs Python3 (!).
I got it working (up to a point) when I used apt get to install Python2.7, but then I got other errors as mentioned in that PR.
There was a problem hiding this comment.
So at which point exactly do we need Python2.7? should we try wrapping the start and test scripts in dockerfiles? The Dockerfile I'm using for dev seems to work well.
There was a problem hiding this comment.
It's very strange. I think most of the gcloud toolchain runs on Python3, but the dev_appserver is something they actually want to get rid of, but so many real customers use it that they can't - but it runs on 2.7 and they don't want to invest into upgrading. Something like that.
There was a problem hiding this comment.
I'm surprised. If you look at the Dockerfile I added, it doesn't explicitly use Python2.7 at all but it definitely brings up the API and admin apps successfully (was testing it last night).
I can't see why it works in the Dockerfile and wouldn't work in the pipeline.
2 participants
No description provided.