John Sirois

@photoroman I just maintain Pex and the underlying technology of scies; not Pants or scie-pants. That said, I used to work on Pants and know it relies on file system...

Limitations of Pants stack I know of: 1. scie-pants file locking (via [scie-jump](https://github.com/a-scie/jump) to support safe concurrent scie execution, defaults to `~/.caches/nce` on Linux, `~/Library/Caches/nce` on Mac, can be relocated...

@jberkel there is not. There used to be (https://docs.pex-tool.org/api/vars.html#PEX_ALWAYS_CACHE, https://docs.pex-tool.org/api/vars.html#PEX_FORCE_LOCAL and https://docs.pex-tool.org/api/vars.html#PEX_UNZIP), because eggs were importable in zipped form, but wheels, in the general case, are not (you can't dlopen...

@CMLivingston since you have a user base that feels this pain point acutely, perhaps you can poll them and suggest some exact wording / layout for the error message on...

I think this can be closed as implemented in the absence of further details about the original request. Both the PEX bootstrap behavior (trying all available interpreters for bootstrapping if...

Instead of embedding a file we could just set custom PexInfo.build_properties from the Pants side: https://github.com/pantsbuild/pex/blob/ea57f59773ca64d8415194d23720b5e5fb4378ec/pex/pex_info.py#L153-L158

> that is my original intent... to use the pex info build properties and pass the content for it from pants to pex using a json file Ah, ok. The...

Pex infra here: https://github.com/pex-tool/pex/pull/3036 I'll update when this is released in Pex 2.74.0. Released here: https://github.com/pex-tool/pex/releases/tag/v2.74.0

This issue really has nothing to do with loading plugins, just resolving them.

Aha - ok. Yeah, I had actually started down an experimental road supporting implicit output targets ala bazel for this. The idea would be `plugins = ["//this/is/a/target.wheel"]`. So, a target...