refactor(pypi): split out a hub_builder helper from the extension code (#3243) This is a somewhat tedious refactor, where I am just moving code around (and sometimes renaming various parameters). I am not modifying and/or fixing any bugs other than more error messages in one place since I noticed there was a lack of validation. The main idea is to create a `hub_builder` so that we could also use it for `pip.configure` calls and/or use it for `py.lock` file parsing and reuse code. I hope that moving it to a separate file makes it a little bit more obvious what pieces are used to create a hub repository. What is more, since the pip extension is reproducible, I have removed some code that was sorting the output. Work towards #2747 --------- 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.