Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

I'm curious: does anyone else use a `pex_binary` to generate a "self-extracting virtualenv archive"?

I wrote an entry point (actually an "executable") for a pex that just makes the pex extract itself. I wonder if that is a common pattern or not. Here's where I'm adding the `pex_binary(executable=...)` : <https://github.com/StackStorm/st2/pull/6307>

I use PEX_TOOLS=1 venv tricks all over the place for Docker and various other deployments

Have you ever added a script to the pex that makes merely running it unpack it?

Hmm, oh like a script that re-execs with PEX_TOOLS so it acts like ye old 90s self extracting zip file?  I have not but that sounds cool

The PR I linked to does that :stuck_out_tongue:

I did a few quirky things to remove the script from the venv after unpacking, but oh well. (I have the script in a `packaging/` directory, so it ends up in the venv merged with the `packaging` package. I didn't want that hanging around.)