Skip to content

Conversation

@brandonchinn178
Copy link
Contributor

@brandonchinn178 brandonchinn178 commented Jun 16, 2025

Repro for #87, not fixed yet

$ (cd examples/multi-version && bazel build //...)
DEBUG: /private/var/tmp/_bazel_bchinn/580a5fb098a03d2587c5d0fb27537737/external/rules_python~/python/private/config_settings.bzl:200:14: The current configuration rules_python config flags is:
    @@rules_python~//python/config_settings:pip_whl: "auto"
    @@rules_python~//python/config_settings:pip_whl_glibc_version: ""
    @@rules_python~//python/config_settings:pip_whl_muslc_version: ""
    @@rules_python~//python/config_settings:pip_whl_osx_arch: "arch"
    @@rules_python~//python/config_settings:pip_whl_osx_version: ""
    @@rules_python~//python/config_settings:py_freethreaded: "no"
    @@rules_python~//python/config_settings:py_linux_libc: "glibc"
    @@rules_python~//python/config_settings:python_version: "3.11"

If the value is missing, then the default value is being used, see documentation:
https://rules-python.readthedocs.io/en/latest/api/rules_python/python/config_settings
ERROR: /private/var/tmp/_bazel_bchinn/580a5fb098a03d2587c5d0fb27537737/external/rules_python~~pip~pip_A/cachetools/BUILD.bazel:5:12: configurable attribute "actual" in @@rules_python~~pip~pip_A//cachetools:_no_matching_repository doesn't match this configuration: No matching wheel for current configuration's Python version.

The current build configuration's Python version doesn't match any of the Python
wheels available for this distribution. This distribution supports the following Python
configuration settings:
    //_config:is_cp310

To determine the current configuration's Python version, run:
    `bazel config <config id>` (shown further below)

For the current configuration value see the debug message above that is
printing the current flag values. If you can't see the message, then re-run the
build to make it a failure instead by running the build with:
    --@@rules_python~//python/config_settings:current_config=fail

However, the command above will hide the `bazel config <config id>` message.


This instance of @@rules_python~~pip~pip_A//cachetools:_no_matching_repository has configuration identifier 7170974. To inspect its configuration, run: bazel config 7170974.

For more help, see https://bazel.build/docs/configurable-attributes#faq-select-choose-condition.

ERROR: Analysis of aspects '[//:py.bzl%mypy_aspect] with parameters {} on //a:generate_requirements_lock' failed; build aborted: Loading failed
INFO: Elapsed time: 2.432s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully

aspect()'s new propagation_predicate might help here, but it'll only be available Bazel 9+

@brandonchinn178
Copy link
Contributor Author

@apalmer-theorem Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant