tree 65f49caa02ceba89ea93123cdad9e26c7bbfcd04
parent 6bcee35fd72af6c7374318ab24aa71367e5100be
author Ignas Anikevicius <ignas.anikevicius@woven-planet.global> 1676091753 +0900
committer GitHub <noreply@github.com> 1676091753 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJj5yFpCRBK7hj4Ov3rIwAAyf8IAGW22gpUcdn/AVFLR+H/A4qi
 8+knmnGtG6sAU66oscvX6nKD7hIUwWBDILSWnwjByMW4G0DpOy6MZDLvD2307KNP
 T6BytMv4HEF/ldQZEq6WObzrZkeDkQjvmSJHwi4/9f12GYx24o4KDo5vRE+TEugF
 8mS5JZI8eLyF2b4jVu5tQY+wr1qSVQhV1SqeEf6JdOnfpjbV4z5fFOM1KrrDEPig
 DStOFqNt0VE709XDHuyG6GUcBHkO4LrTbPQQ1U0OgCMl+2xl0LzCA/qO4Ez2o1n8
 vI1hPBry9cXqAruBGCzwxiP3tjP/JX2zXI0r2jv+j3xXmBgJpZ8vJ2FztEqxBaI=
 =V5UG
 -----END PGP SIGNATURE-----
 

fix: make py_proto_library respect PyInfo imports (#1046)

py_proto_library has an implicitly dependency on the protobuf client runtime, and it was ending up in runfiles, but it wasn't imported because the `imports` value it was setting wasn't be propagated.

To fix, make py_proto_library properly propagate the imports attribute the protobuf client runtime so that the libraries are added to sys.path correct.

Also adds an example for bzlmod and old way of using the py_proto_library as a test.

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>