bazel: Set --incompatible_default_to_explicit_init_py

Bug: b/266950138 Change-Id: Ifc643a01ddc49e77c6180711ec73e73911e4740c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/180454 Presubmit-Verified: CQ Bot Account <[email protected]> Reviewed-by: Armando Montanez <[email protected]> Pigweed-Auto-Submit: Ted Pudlik <[email protected]> Commit-Queue: Auto-Submit <[email protected]>
pauschar · Nov 10, 2023 · 29b0e93 · 29b0e93
1 parent e596056
commit 29b0e93
Showing 1 changed file with 9 additions and 0 deletions.
diff --git a/.bazelrc b/.bazelrc
@@ -19,6 +19,15 @@
 common --per_file_copt=external/.*@-w
 common --host_per_file_copt=external/.*@-w
 
+# Don't automatically create __init__.py files.
+#
+# This prevents spurious package name collisions at import time, and should be
+# the default (https://github.com/bazelbuild/bazel/issues/7386). It's
+# particularly helpful for Pigweed, because we have many potential package name
+# collisions due to a profusion of stuttering paths like
+# pw_transfer/py/pw_transfer.
+common --incompatible_default_to_explicit_init_py
+
 # Required for new toolchain resolution API.
 build --incompatible_enable_cc_toolchain_resolution