You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies, just noticed your error is not related to containerregistry (which was my initial thought as its the source of most of my issues related to python).
We will soon be deprecating build.py as a means to drive building our containers, so we're not actively making improvements to this script.
Note that build.py just calls those targets and does a couple of additional things (uploading the container to gcr and uploading a tar file to gcs), so for most use cases, building the container directly using the Bazel targets should suffice. Note, however, that when running these targets you might run into other issues related to py2/py3 compatibility with the container_image targets that are executed by the toolchain rules, due to containerregistry not being compatible with py3.
If you are really set on using build.py, it should be feasible to get it to be compatible with py3. I'll be happy to review any PRs you send for that purpose.
Could you also please elaborate a bit more about your use case (i.e., why do you want to build these containers?)
flake8 testing of https://github.com/bazelbuild/bazel-toolchains on Python 3.7.1
$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
The text was updated successfully, but these errors were encountered: