Skip to content

Disable legacy implicit __init__.py generation by default #438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tameware wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Disable legacy implicit __init__.py generation by default #438

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .bazelrc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,15 @@ common --enable_platform_specific_config
# bazelisk mod deps --lockfile_mode=update
common --lockfile_mode=error

# rules_python 2.4+ warns on deprecated implicit __init__.py creation for every
# py_* target that still uses the legacy path — including dependencies we do
# not control (rules_python's own tools, emsdk wasm_binary, bazel_tools JDK
# helpers). This flag turns the legacy path off workspace-wide so those
# warnings stay quiet. Remove it once those dependencies ship explicit-init
# defaults (or set legacy_create_init = 0 on their py_* targets); see
# bazel-contrib/rules_python#2945.
build --incompatible_default_to_explicit_init_py

# We build nothing for Android, but rules_jvm_external (the //jni Maven jar)
# depends on rules_android, whose android_sdk_repository extension probes
# $ANDROID_HOME while analyzing *any* target. When ANDROID_HOME is exported but
Expand Down
Loading