John Sirois

Confirming this is the issue. For this CI run: https://github.com/pantsbuild/scie-pants/actions/runs/3679714653/jobs/6224494867#step:6:147 We get: ``` >> Verifying the tools.pex built by the package crate matches the tools.pex built by Pants The tools.pex...

@jasondamour your suspicion is correct. The problem is specifically with the use of the `setuptools.setup` `setup_requires` argument which was a big part of the motivation for PEP-518. See here for...

@shanipribadi what @rhuanbarreto says is true, you need Pex 2.28.1 or newer. My test rig just uses 2 files: `pants.toml` and `BUILD`: + `pants.toml`: ```toml [GLOBAL] pants_version = "2.24.2" backend_packages...

@rhuanbarreto this is not completely true: > It's a zipapp with a python shebang on the entrypoint. It's a zipapp with a `#!/bin/sh` shebang. I have a note above about...

> and the thing we're not doing is materializing the correct files out (today) Well, you are iff the user is curious enough or knowledgable enough to use `pex_binary(output_path="anything_with_no'.pex'_extension_at_the_end")`. This...

Well, I am not so LOL about all this. Pants seems to envelop users and developers in a cloud of not understanding anything or trying to very hard. I agree...

Oh, right, and continuing with the above test rig: ```console # Clean slate: :; rm -rf dist/ :; pants --pex-cli-version=v2.28.1 package :cowsay 17:08:43.15 [INFO] Wrote dist/cowsay :; ls -1sh dist/...

OK, https://github.com/a-scie/jump/pull/283 will allow the more useful / less messy: ```console SCIE=split dist/cowsay dist -- pex ``` That will just split out the pex. Back on the Pex side I'll...

Alright, support for splitting a PEX scie's PEX out individually and that PEX having the expected names and perms is now all available in https://github.com/pex-tool/pex/releases/tag/v2.33.3.

The build uses the setuptools `setup_requires` kwarg to try to get `setuptools_scm` available. This has been long known to be a problem and PEP-517/518 came along time ago now to...