Is anyone in the flyte community currently using pants as their build system? In particular, curious if there are any particular considerations for running flyte workloads that are packaged as pex binaries

Cc @Kutta Srinivasan knows about pants

We used buck at Meta and built single-file python archive files (FB-specific versions of PARs) which included all static dependencies (mostly C++ and other common libs, no dynamic linking). I'm not familiar with pants unfortunately

Pants is very similar (uses pex instead of PARs but the principle is the same). I'll give it a shot and report back