cleanup stale docs

Author: aignas

python/private/common.bzl

@@ -396,8 +396,7 @@ def create_py_info(
         implicit_pyc_files: {type}`depset[File]` Implicitly generated pyc files
             that a binary can choose to include.
         imports: depset of strings; the import path values to propagate.
-        venv_symlinks: {type}`list[tuple[str, str, str]]` tuples of
-            `(normalized_package_name, runfiles_path, site_packages_path)` for
+        venv_symlinks: {type}`list[VenvSymlinkEntry]` instances for
             symlinks to create in the consuming binary's venv.
 
     Returns:

python/private/py_info.bzl

@@ -303,22 +303,6 @@ This field is currently unused in Bazel and may go away in the future.
 
 A depset with `topological` ordering.
 
-
-Tuples of `(runfiles_path, site_packages_path)`. Where
-* `runfiles_path` is a runfiles-root relative path. It is the path that
-  has the code to make importable. If `None` or empty string, then it means
-  to not create a site packages directory with the `site_packages_path`
-  name.
-* `site_packages_path` is a path relative to the site-packages directory of
-  the venv for whatever creates the venv (typically py_binary). It makes
-  the code in `runfiles_path` available for import. Note that this
-  is created as a "raw" symlink (via `declare_symlink`).
-* `symlink_key` is a path which should be checked instead of the
-  `site_packages_path`. This is typically used for dist-info directories as
-  they include version in the filenames and we want to ensure that we can
-  replace the whole package and not have orphan .dist-info packages in the
-  virtual environment.
-
 :::{include} /_includes/experimental_api.md
 :::