cleanup docs and example WORKSPACE files

Author: aignas

docs/pypi/download-workspace.md

@@ -7,7 +7,7 @@
 Using PyPI packages (aka "pip install") involves the following main steps:
 
 1. [Generating requirements file](./lock)
-2. Installing third-party packages in [bzlmod](./download) or [WORKSPACE](./download-workspace).
+2. Installing third-party packages in [bzlmod](./download).
 3. [Using third-party packages as dependencies](./use)
 
 With the advanced topics covered separately:
@@ -17,7 +17,6 @@ With the advanced topics covered separately:
 ```{toctree}
 lock
 download
-download-workspace
 use
 ```
 

docs/pypi/index.md

@@ -1,66 +0,0 @@
-workspace(name = "rules_python_multi_python_versions")
-
-local_repository(
-    name = "rules_python",
-    path = "../..",
-)
-
-load("@rules_python//python:repositories.bzl", "py_repositories", "python_register_multi_toolchains")
-
-py_repositories()
-
-default_python_version = "3.10"
-
-python_register_multi_toolchains(
-    name = "python",
-    default_version = default_python_version,
-    python_versions = [
-        "3.10",
-        "3.11",
-        "3.12",
-        "3.13",
-        "3.14",
-    ],
-    register_coverage_tool = True,
-)
-
-load("@python//:pip.bzl", "multi_pip_parse")
-
-multi_pip_parse(
-    name = "pypi",
-    default_version = default_python_version,
-    python_interpreter_target = {
-        "3.10": "@python_3_10_host//:python",
-        "3.11": "@python_3_11_host//:python",
-        "3.12": "@python_3_12_host//:python",
-        "3.13": "@python_3_13_host//:python",
-        "3.14": "@python_3_14_host//:python",
-    },
-    requirements_lock = {
-        "3.10": "//requirements:requirements_lock_3_10.txt",
-        "3.11": "//requirements:requirements_lock_3_11.txt",
-        "3.12": "//requirements:requirements_lock_3_12.txt",
-        "3.13": "//requirements:requirements_lock_3_13.txt",
-        "3.14": "//requirements:requirements_lock_3_14.txt",
-    },
-)
-
-load("@pypi//:requirements.bzl", "install_deps")
-
-install_deps()
-
-load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
-
-# See https://github.com/bazelbuild/rules_shell/releases/tag/v0.2.0
-http_archive(
-    name = "rules_shell",
-    sha256 = "410e8ff32e018b9efd2743507e7595c26e2628567c42224411ff533b57d27c28",
-    strip_prefix = "rules_shell-0.2.0",
-    url = "https://github.com/bazelbuild/rules_shell/releases/download/v0.2.0/rules_shell-v0.2.0.tar.gz",
-)
-
-load("@rules_shell//shell:repositories.bzl", "rules_shell_dependencies", "rules_shell_toolchains")
-
-rules_shell_dependencies()
-
-rules_shell_toolchains()

examples/multi_python_versions/WORKSPACE

@@ -1,65 +0,0 @@
-workspace(name = "rules_python_pip_parse_example")
-
-local_repository(
-    name = "rules_python",
-    path = "../..",
-)
-
-load("@rules_python//python:repositories.bzl", "py_repositories", "python_register_toolchains")
-
-py_repositories()
-
-python_register_toolchains(
-    name = "python_3_9",
-    python_version = "3.9.25",
-)
-
-load("@rules_python//python:pip.bzl", "pip_parse")
-
-pip_parse(
-    # (Optional) You can set an environment in the pip process to control its
-    # behavior. Note that pip is run in "isolated" mode so no PIP_<VAR>_<NAME>
-    # style env vars are read, but env vars that control requests and urllib3
-    # can be passed
-    # environment = {"HTTPS_PROXY": "http://my.proxy.fun/"},
-    name = "pypi",
-
-    # Requirement groups allow Bazel to tolerate PyPi cycles by putting dependencies
-    # which are known to form cycles into groups together.
-    experimental_requirement_cycles = {
-        "sphinx": [
-            "sphinx",
-            "sphinxcontrib-qthelp",
-            "sphinxcontrib-htmlhelp",
-            "sphinxcontrib-devhelp",
-            "sphinxcontrib-applehelp",
-            "sphinxcontrib-serializinghtml",
-        ],
-    },
-    # (Optional) You can provide extra parameters to pip.
-    # Here, make pip output verbose (this is usable with `quiet = False`).
-    # extra_pip_args = ["-v"],
-
-    # (Optional) You can exclude custom elements in the data section of the generated BUILD files for pip packages.
-    # Exclude directories with spaces in their names in this example (avoids build errors if there are such directories).
-    #pip_data_exclude = ["**/* */**"],
-
-    # (Optional) You can provide a python_interpreter (path) or a python_interpreter_target (a Bazel target, that
-    # acts as an executable). The latter can be anything that could be used as Python interpreter. E.g.:
-    # 1. Python interpreter that you compile in the build file (as above in @python_interpreter).
-    # 2. Pre-compiled python interpreter included with http_archive
-    # 3. Wrapper script, like in the autodetecting python toolchain.
-    #
-    # Here, we use the interpreter constant that resolves to the host interpreter from the default Python toolchain.
-    python_interpreter_target = "@python_3_9_host//:python",
-
-    # (Optional) You can set quiet to False if you want to see pip output.
-    #quiet = False,
-    requirements_lock = "//:requirements_lock.txt",
-    requirements_windows = "//:requirements_windows.txt",
-)
-
-load("@pypi//:requirements.bzl", "install_deps")
-
-# Initialize repositories for all packages in requirements_lock.txt.
-install_deps()