move func doc to docstring

Author: rickeylev

python/private/site_init_template.py

@@ -124,12 +124,15 @@ def _search_path(name):
     return None
 
 
-# NOTE: We do not add _RUNFILES_ROOT to sys.path for two reasons:
-# 1. Under workspace, it makes every external repository importable. If a Bazel
-#    repository matches a Python import name, they conflict.
-# 2. Under bzlmod, the repo names in the runfiles directory aren't importable
-#    Python names, so there's no point in adding the runfiles root to sys.path.
 def _setup_sys_path():
+    """Perform Bazel/binary specific sys.path setup.
+
+    NOTE: We do not add _RUNFILES_ROOT to sys.path for two reasons:
+    1. Under workspace, it makes every external repository importable. If a Bazel
+       repository matches a Python import name, they conflict.
+    2. Under bzlmod, the repo names in the runfiles directory aren't importable
+       Python names, so there's no point in adding the runfiles root to sys.path.
+    """
     seen = set(sys.path)
     python_path_entries = []
 
@@ -200,12 +203,15 @@ def _maybe_add_path(path):
     return coverage_setup
 
 
-# The pyvenv.cfg created for py_binary leaves the `home` key unset. A
-# side-effect of this is `sys._base_executable` points to the venv executable,
-# not the actual executable. This mostly doesn't matter, but does affect
-# using the venv module to create venvs (they point to the venv executable, not
-# the actual executable).
 def _fixup_sys_base_executable():
+    """Fixup sys._base_executable to account for Bazel-specific pyvenv.cfg
+
+    The pyvenv.cfg created for py_binary leaves the `home` key unset. A
+    side-effect of this is `sys._base_executable` points to the venv executable,
+    not the actual executable. This mostly doesn't matter, but does affect
+    using the venv module to create venvs (they point to the venv executable, not
+    the actual executable).
+    """
     # Must have been set correctly?
     if sys.executable != sys._base_executable:
         return