tree 620aee70e4663420f695d08980090fc5966cb1b7
parent eca368af58ec8368fe3ba5422f2617e389481ce6
author Siddhartha Bagaria <starsid@gmail.com> 1703067079 +0900
committer GitHub <noreply@github.com> 1703067079 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlgr3WCRBK7hj4Ov3rIwAAEPQIALIdZGOwPAEy/5tH9FxwZkI2
 95CBsnIKzXyKmeU602os34OoJ8hgdxpHgSQIqXBhdgMeaQBhUrbXrdeEHT5CFZEP
 UVb6DekZNFJpvpEJkH/rscK7TU+Nh/O15o15qyoeJaDoW1XuOsM7/AQKCGoOlJOi
 gsdf2VXREGWE4sD7SIIkJypr2tZtTntmGyEnj7kiW2Ua4nnmw8LQg05aGUxrqCVG
 QyuplIwlq3YrKLijfoEXF3mIeTStHcHb7uC+rmKmBug6B7PsEm5kJ1aKuy2pwvJD
 ZORvcVS86PxNNCrJxxg3O3KQh4Dt/0uYDebWzo15ShrGQY3B8zadDuzS0HmNRt0=
 =YSPq
 -----END PGP SIGNATURE-----
 

fix(gazelle): __init__.py in per-file targets (#1582)

As per Python spec, `__init__.py` files are depended upon by every file
in the package, so let's make sure that our generated targets also
understand this implicit dependency. Note that because Python module
dependencies are not a DAG, we can not depend on the Bazel target for
`__init__.py` files (to avoid cycles in Bazel), and hence a non-empty
`__init__.py` file is added to the `srcs` attribute of every
`py_library` target.

The language spec also says that each package depends on the parent
package, but that is a less commonly used feature, and can make things
more complex.

From [importlib] docs:
> Changed in version 3.3: Parent packages are automatically imported.

From [import] language reference:
> Importing parent.one will implicitly execute parent/__init__.py and
parent/one/__init__.py.


[importlib]:
https://docs.python.org/3/library/importlib.html#importlib.import_module
[import]:
https://docs.python.org/3/reference/import.html#regular-packages

---------

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>