diff options
author | Jon Brandvein <brandjon@google.com> | 2019-07-26 23:14:09 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-07-26 23:14:09 -0400 |
commit | d1596a309ac9216b1a17fc984eb1376e64aa5fcf (patch) | |
tree | 6a03ad1eba2c01a77dee0280a82ebcb4f303376b /WORKSPACE | |
parent | d852e8a063b83f1c75c2cf0bcba1a0f9e54e62d0 (diff) | |
download | bazelbuild-rules_python-d1596a309ac9216b1a17fc984eb1376e64aa5fcf.tar.gz |
Rename canonical workspace name to "@rules_python" (#212)
* Change official workspace name to @rules_python
This includes regenerating the par files to use the new name. Neat trick: Since
the par file regeneration depends on the previous par files, I had to bootstrap
this change by temporarily editing the WORKSPACE to include:
local_repository(
name = "io_bazel_rules_python",
path = ".",
)
* Add a nice error message to help with the workspace name migration
This hooks into pip_repositories(), which users are *supposed* to be calling in
their WORKSPACE files, to emit a nice fail() message alerting them that they
need to update their repo definition.
Without this change (and even with it, for users who do not call
`pip_repositories()`), users will instead see a confusing cyclic dependency
error.
Diffstat (limited to 'WORKSPACE')
-rw-r--r-- | WORKSPACE | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -12,7 +12,7 @@ # See the License for the specific language governing permissions and # limitations under the License. -workspace(name = "io_bazel_rules_python") +workspace(name = "rules_python") load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository") load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_file") |