[PATCH] D113773: Don't define //mlir:MLIRBindingsPythonCore in terms of the NoCAPI and CAPIDeps targets.

[Geoffrey Martin-Noble via Phabricator via llvm-commits]

GMNGeoffrey accepted this revision.
GMNGeoffrey added a comment.
This revision is now accepted and ready to land.

Is there something special about Google's internal version of Bazel that would make this different? Or just that's where you noticed it and it's a potential problem in OSS as well? I want to make sure we're making the decisions that make the most sense for Bazel users (the differences between Bazel and Blaze are on Google(rs) to figure out IMO)


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D113773/new/

https://reviews.llvm.org/D113773