Aha

self.context.products.is_required_data

looks like the thing

<!channel> simple question, how do I use

resources

from a

python_binary

? I.e.

resources(name='resources',
          sources=['foo.txt'])

python_binary(name='foo',
              source='foo.py',
              dependencies=[':resources'])

(I'd avoid using a broad notification like that)

people who are paying attention and can answer will answer

oops, my bad

Wasn't sure what the protocol was here

just general etiquette 🙂 IRC didn't let you highlight a whole channel but people generally reacted badly to being highlighted individually for general questions

oh wow

thank you for reminding me this thing exists 😛

is @enough-analyst-54434 still among the living?

he is! but he's been in the desert all winter, heh

mostly at red rocks

@witty-crayon-22786 you’re alive!

Should

from pkg_resources import resource_string

if __name__ == '__main__':
    print resource_string(__name__, 'foo.txt')

work? given my BUILD file above?

I think resources didn’t work on python binary targets and I had a PR that I didn’t update since I changed jobs since writing it.

Let me dig that up

resources(name='resources',
	  sources=['foo.txt'])

python_library(name='lib',
               dependencies=[':resources'])

python_binary(name='foo',
              source='foo.py',
              dependencies=[':lib'])

didn't seem to work either

do the resources end up in the final pex at all as shown by a

unzip -l the.pex

?

Oh I remember the issue, it was a problem when building multiple pex at the same time: https://github.com/pantsbuild/pants/pull/3993/files and the dead rb https://rbcommons.com/s/twitter/r/4331/diff/1#index_header, which looks like it’s still an issue, will clean up the review.

nope

is there any workaround?

It might not be related, how are you running it?

I've tried

./pants binary src/py/support:foo

and

run

It shouldn’t be related unless you’re building multiple pex. Try nuking your caches and rebuilding?

What's the easiest way to to ^? Just

rm -rf dist/*

?

There might be something in your local artifact cache if you’ve configured it (

./pants options | grep cache

) but I’m actually not sure if python binary create writes anything there.

I have a question about general Monorepo philosophy (and as it relates to build failures). Would this be the right place to ask that question? We are primarily a scala-major code repo.

I think so. What’s the question?