Can I have a resources dir like this:

test
+- resources
     +- co
         +- foo1
              +- BUILD
         +- foo2
              +- BUILD

From what I can tell the created jar has a structure I don’t understand - it looks like everything is rooted at

resources

and it has the full dir structure inside

I thought I’d have two resource jars that contained only the contents of

foo1

and

foo2

@rich-helicopter-79006 : (re)sources are relative to the nearest "source root": http://www.pantsbuild.org/setup_repo.html#source-roots

test/$lang

is one of the default configured source root patterns

namespacing resources is a good practice for cases where a library uses the resource. less important for binaries and tests.

oic. Thank you

So…if I wanted to have a library that only contained resources specific to it, what is the best practice?

namespace it.

Is it to do something like:

test
+- co
     +- foo1
          +- resources
              +- BUILD

wherever possible.

er, no: that's not namespaced

Oh - you mean namespace it inside the global resources folder and refer to it via namespaced

yea

co/foo1/name

is less likely to collide than

name

, so where possible prefer the former.

And the BUILD file - should I have different resources targets or one that contains everything?

if you need the latter thing, yea: the second structure you pasted would just result in

name

as with sources, split them up based on who uses them

Gotcha. Either way, if it’s namespaced I’ll end up with a jar with only the relevant files in the namespace

Thanks @witty-crayon-22786

$ ./pants run bonsai/.buildkite
Exception caught: (<class 'pants.build_graph.address_mapper.InvalidBuildFileReference'>)

Exception message: [...]/bonsai/.buildkite does not contain any BUILD files.
  when translating spec bonsai/.buildkite

and yet:

$ cat bonsai/.buildkite/BUILD
python_binary(
  name = 'generate-backend-deploy-step',
  dependencies=[
    '3rdparty/python/sh',
  ],
  source='generate-backend-deploy-step.py',
)

am i missing something obvious?

hmm, removing the

.

prefix makes it work

is that intentional or a bug?

doesn’t quite answer your question vis a vis intentional - but some discussion/work around instructions here: https://github.com/pantsbuild/pants/issues/4547#issuecomment-299048599

Does anyone know if there are any Pants plugins that support Cython or C extensions?

ah thank you @flat-pizza-44400

@fancy-forest-37893 do you mean a pants plugin that uses a cython or c ext, or one that supports modeling and building them?

One that supports building them

My use case would be to build cythonized python code and then put the results into a PEX file