tree 39cbeee0cfb0f5dd914a2f4194e609154bc920fd
parent 231d3f633fbcbb36028d96a188298df99bf153e1
author Nikolaus Wittenstein <nikolaus.wittenstein@gmail.com> 1704758946 -0800
committer GitHub <noreply@github.com> 1704758946 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlnI6yCRBK7hj4Ov3rIwAA2u4IADdCbgX/KY7oM2cKg8r+LgYX
 uScrujyhZUvW2vZemb0d5MHkSAnyCHwS7mY4Mui4L35ygzL5GqAJ1GPaWOHnlpRp
 dhk+YdfbpPNeFBoiaEjAxO1mBbPWiCLXsy54e7RT5WK9zitB51dKBzefgLGQN9Gv
 E1zFk0HKTSnhICvJtfiMtPNMGoYo9raAmxHNPUXbX+/F9uJuDFipK1CrPMXoBHCh
 3WhkvPktdB93DH7CxRmt2mlWzzzVAzLX9k2JJD8+/fA/gvU/duzmZ+kXwuISo3MM
 oKpmDLEj24+YG8fAUX9twhO6rNmmLZKNviqfTOmcEg9isXKgPVn2L4w+JHbSWnY=
 =1+B+
 -----END PGP SIGNATURE-----
 

fix: Fix per-file config interaction with one py_binary per main (#1664)

[This previous PR](https://github.com/bazelbuild/rules_python/pull/1584)
added the ability to make a `py_binary` target per file if `if __name__
== "__main__"` tokens were found in the file. This works great in the
default case, but when `python_generation_mode` is set to `file`, the
plugin now attempts to make both a `py_binary` and a `py_library` target
for each main file, which results in an error.

This PR modifies the behavior to work properly with per-file target
generation, and adds tests for this case.