Weird way to use the provider in pyz_binary

[nicolov]

Thanks a lot for the code, it's really useful!

I've noticed that pyz_binary uses the provider in a weird way. Usually, these leaf nodes just consume the transitive info, and can do:

for dep in ctx.attr.deps:
    for mapping in dep[PyZProvider].transitive_mappings:
        links[....

This is an updated reference for the canonical way to set this up.

[evanj]

Thanks for the note. I ... do not recall why exactly I did it this way.

We've decided to not use Bazel, so this is basically unmaintained. I am unfortunately not going to have the time to figure out why it was done like this and try to fix it. Sorry.