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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Looks like //tests:version_test relies on a custom flag to get the Python version. It should use @bazel_tools//tools/python:PY[2|3]. This may cause problems once --incompatible_use_python_toolchains is enabled (#98).
The text was updated successfully, but these errors were encountered:
This adds a hook file for run_tests.sh to write toolchain info to before each bazel invocation. This replaces the legacy way of passing an interpreter in via --python_path.
It also replaces a config_setting that was used to control whether PY2 or PY3 was used, with a simple constant symbol consumed at loading time. This is needed in order to make the target aware at analysis time of which version it is building for.
Fixes#98, fixes#102.
This adds a hook file for run_tests.sh to write toolchain info to before each bazel invocation. This replaces the legacy way of passing an interpreter in via --python_path.
It also replaces a config_setting that was used to control whether PY2 or PY3 was used, with a simple constant symbol consumed at loading time. This is needed in order to make the target aware at analysis time of which version it is building for.
Fixes#98, fixes#102.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looks like
//tests:version_test
relies on a custom flag to get the Python version. It should use@bazel_tools//tools/python:PY[2|3]
. This may cause problems once--incompatible_use_python_toolchains
is enabled (#98).The text was updated successfully, but these errors were encountered: