-
-
Notifications
You must be signed in to change notification settings - Fork 610
Labels
cleanupTech debt, resolving it improves our own velocityTech debt, resolving it improves our own velocity
Description
🐞 bug report
Description
A clear and concise description of the problem...After updating from bazel 6.5.0 to bazel 8.3.1 and from WORKSPACE to bzlmod I started getting a bunch of warnings which look like the one below. Have I misconfigured my environment or rules_python
is using some deprecated code? The relevant part of MODULE.bazel
looks like:
bazel_dep(name = "rules_python", version = "1.5.1")
python = use_extension("@rules_python//python/extensions:python.bzl", "python")
python.toolchain(
is_default = True,
python_version = "3.10",
)
pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
hub_name = "pip-build",
python_version = "3.10",
requirements_lock = "//:build_support/python/requirements.txt.lock",
)
use_repo(pip, "pip-build")
🔥 Exception or Error
WARNING: /scratch/nikolay_nikolov/.cache/bazel/_bazel_nikolay_nikolov/79bf5e678fbb2019f1e30944a206f079/external/rules_python++pip+pip-build_310_debugpy/BUILD.bazel:5:20: in _copy_file rule @@rules_python++pip+pip-build_310_debugpy//:_cp
_19_namespace: target '@@rules_python++pip+pip-build_310_debugpy//:_cp_19_namespace' depends on deprecated target '@@bazel_tools//src/conditions:host_windows_x64_constraint': No longer used by Bazel and will be removed in the future. Mi
grate to toolchains or define your own version of this setting
🌍 Your Environment
Operating System:
Distributor ID: Debian
Description: Debian GNU/Linux 13 (trixie)
Release: 13
Codename: trixie
Output of bazel version
:
Build label: 8.3.1
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Jun 30 16:23:40 2025 (1751300620)
Build timestamp: 1751300620
Build timestamp as int: 1751300620
Rules_python version:
1.5.1
Anything else relevant?
Metadata
Metadata
Assignees
Labels
cleanupTech debt, resolving it improves our own velocityTech debt, resolving it improves our own velocity