feat(gazelle) Remove entry point file requirements when generating rules (#2998) Remove entry point file requirements when generating rules. Enable python rule generation as long as there are .py source files under the directory so all new packages will have python rules generated in the package. The extension used to require entrypoints for generation but: - entry point for tests (i.e., `__test__.py` ) is no longer required after https://github.com/bazel-contrib/rules_python/pull/999 and https://github.com/bazel-contrib/rules_python/pull/2044 - entry point for binaries (i.e., `__main__.py` ) is no longer required after https://github.com/bazel-contrib/rules_python/pull/1584 The entry point for libraries (`__init__.py` ) shouldn't be required either, especially for Python 3.3 and after when namespace packages are supported. --------- Co-authored-by: yushan <yushan@uber.com> Co-authored-by: Douglas Thor <dougthor42@users.noreply.github.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.