fix(local_runtime): Improve local_runtime usability in macos / windows (#3148) local_runtime fails to handle many variations of python install on Windows and MacOS, such as: * LDLIBRARY on MacOS may refer to a file under PYTHONFRAMEWORKPREFIX, not LIBDIR * LDLIBRARY on Windows refers to pythonXY.dll, not the linkable pythonXY.lib * LIBDIR may not be correctly set on Windows. * On windows, interpreter_path needs to be normalized. Other paths also require this. * SHLIB_SUFFIX does not indicate the correct suffix. For examples, see: https://docs.python.org/3/extending/windows.html In order to resolve this the shared library resolution has been moved into get_local_runtime_info.py, which now does the following: * Constructs a list of paths to search based on LIBDIR, LIBPL, PYTHONFRAMEWORKPREFIX, and the executable directory. * Constructs a list of libraries to search based on INSTSONAME, LDLIBRARY, pythonXY.lib, etc. * Checks to see which files exist, partitioning the result into a list of "dynamic_libraries" and "static_libraries" On Windows and macOS, since SHLIB_SUFFIX does not always indicate the filenames needed searching, this has been removed from local_runtime_repo_setup and replaced with an explicit file. On Windows the interpreter_path and other search paths are now normalized (`\` converted to `/`). Additional logging added to local_runtime_repo. Fixes https://github.com/bazel-contrib/rules_python/issues/3055 Work towards https://github.com/bazel-contrib/rules_python/issues/824 --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com>
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.