Release 1.4.8

[jsirois]

User facing issues on the docket:

• non-zip_safe pex extraction has a race on renaming non-zip_safe pex extraction has a race on renaming #557
• Execute pex archive at runtime with -m parameter Execute pex archive at runtime with -m parameter #547
• OSX's python 2.7.10 interpreter reports a bad local platform, bdists fail to resolve OSX's python 2.7.10 interpreter reports a bad local platform, bdists fail to resolve #523
• pex.resolver.resolve does the wrong thing when given an interpreter and no platform pex.resolver.resolve does the wrong thing when given an interpreter and no platform #511
• [Errno 13] Permission denied when executing with bdist_pex [Errno 13] Permission denied when executing with bdist_pex #570

[jakethedev]

The #563 fixes would just so happen to solve a big problem for me right now, we have surprising demand for 'task runners' in python that the -m or -c at runtime would gracefully solve

I'm asking 100% out of curiosity, is there an ETA until this drops? And will -m/-c at runtime work with any future pex artifacts built with 1.4.8?

[jsirois]

I've been aiming for release the last 4 days - today should be the day and we'll support -m and -c at least until python drops or changes support - the ~whole point is to act like a hermetic python interpreter.

NB: Pex has supported (pex --help-varables) the -m behavior via environment variables for a very long time:

$ PEX_MODULE=app:main ./app.pex
$ PEX_MODULE=tool:fix ./app.pex

So the -m support just allows you to switch from the PEX_MODULE env-var to the -m option like python uses.

[jsirois]

Released:

• https://github.com/pantsbuild/pex/releases/tag/v1.4.8
• https://pypi.org/project/pex/1.4.8/