I think I've asked this before, but can I package a pex that just contains the source, without .deps, .bootstrap, or PEX-INFO? Use case is to build a 'working-directory' for Ray on AWS glue.

withput PEX-INFO? do you need any of the pex tools? If not, why not just zip them up using an

archive

target?

Thanks for the reminder 🙂

I’ve not used archive much, but I think it will pull in any sources/files you have as dependencies to it..

Essentially, I want an entrypoint, with its deps, in a zip file, under a single top-level directory. I'll give it a whirl

yea, try it out.

Hmmm... archive only accepts fIle or resource addresses, it ignores anything else.

there is this target that I think could turn your python sources into resources: https://www.pantsbuild.org/docs/reference-experimental_wrap_as_resources 😉

Noice. I don't deserve you, Andreas.

The new (2.17)

python_aws_lambda_function

behaviour gives a zip with those properties, if you pass

include_requirements=False

, I think.

At the root?

Yeah

I'm minded to take a look at that and hack it to do what I need, tbh. I really need two artifacts, one script file, and one zipfile with all the transitive source deps.

Did you ever figure out how to do this? I am looking for pretty much the same. I’d like a zip with all 3rd party dependencies (including locally referenced ones). We use Poetry at the moment for dependency management. The python_aws_lambda_layer target will create a zip of dependencies, however, any locally referenced ones are not added there (they are added to the python_aws_lambda_function target zip). Any help would be greatly appreciated! Thanks!

Yes, specifically for my use case, I have a pants plugin I wrote and can gladly share.

That would be great!

Thank you! Building python stuff for glue is sort of a pain. Haha.