John Sirois

@rahul-theorem there are (at least) 2 axes which can cause a zip to use ZIP64 extensions: size and entry count. If there are >2^16 files in the zip, it will...

I'm going to close this as an answered question. In the meantime two things have improved: 1. Pex now warns when the final PEX zip requires ZIP64 extensions: #2253 2....

This has been a dream since ~day 1 of Pex, it was just too much work to consider. More recent surfacing of this desire has been in #636 and #1007.

Noting that the last PBS release to support 3.7 is https://github.com/indygreg/python-build-standalone/releases/tag/20200822 and that support 3.7.9. Modern PBS releases support 3.8 through 3.11. So Pex could support --par for 3.8 through...

Alright, since `--par` is a Googlism and the real backend is scie; I'm just rolling with `--scie {lazy,eager}` and a few `--scie-*` options for exact control of the PBS Python...

I think with the addition of `--project` in #2455 released in https://github.com/pex-tool/pex/releases/tag/v2.8.0, this issue and the associated project can be closed.

How exactly to word all this is a bit fraught for sure. Current relevant help: ``` pex -h ... Options: --version show program's version number and exit -h, --help show...

I don't repro either the warning line or the import error. I add steps after yours to build a pex file and then dump its metadata so we might compare...

Pex still supports Python 2.7 users, so no. What is your particular interest @ofek? This should mostly be an implementation detail with ~no impact to Pex end users but I'd...

I reject this feature idea for all the reasons mentioned by @kwlzn. In essence, `PEX_PATH` is an incredibly sharp-edged hack. It doesn't need its edge honed further.