Py2/3 generated sources clash in runfiles

[brandjon]

When a target depends on the same generated source file in both PY2 and PY3 modes, it's arbitrary which one wins in the runfiles. Here foobar depends on source file a.py and generated source file b.py through both PY2 and PY3 binary targets. In the runfiles, a.py symlinks to the source file, which is the same in both modes, but b.py symlinks to the file generated in the PY2 output root (the one without "-py3" in the path), silently ignoring the PY3 one.

genrule(
    name = "b",
    outs = [":b.py"],
    cmd = "touch $(location :b.py)",
)

py_binary(
    name = "foo",
    srcs = ["a.py", ":b"],
    main = "a.py",
    default_python_version = "PY3",
)

py_binary(
    name = "bar",
    srcs = ["a.py", ":b"],
    main = "a.py",
    default_python_version = "PY2",
)

sh_binary(
    name = "foobar",
    srcs = [":script.sh"],
    data = [":foo", ":bar"],
)

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!