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
In any case, after extracting the wheel, we should just delete any BUILD or BUILD.bazel files it created. Such files can only cause issues -- there's no way for them to know what version of bazel or rules_python is being used, so they can't reliably define a bazel package. If one exists in a sub-directory, then it will break glob() (it doesn't cross bazel package boundaries).
An issue I've seen happen at least 3 times is a pypi dependency contains a BUILD file, which then breaks the generated Bazel package.
Why this occurs is a bit unclear because the Bazel docs say that BUILD.bazel should take precedence over BUILD
In any case, after extracting the wheel, we should just delete any BUILD or BUILD.bazel files it created. Such files can only cause issues -- there's no way for them to know what version of bazel or rules_python is being used, so they can't reliably define a bazel package. If one exists in a sub-directory, then it will break glob() (it doesn't cross bazel package boundaries).
Related:
The text was updated successfully, but these errors were encountered: