Do not publish wheels for all SHAs, and publish to PyPI from Github Actions.

[stuhood]

This change:

1. Adjusts wheel building to only upload to S3 when requested via a workflow or tag push
2. Adjusts the release job to build and upload wheels to S3, and then also to push them to PyPI.
   • Note that this does not yet publish our "universal" PEX from the CI job, so that step still happens locally.

See the docs changes for a high level overview.

[benjyw]

YAY!

I wonder if we can (with appropriate warning) stop building the pex.

[thejcannon]

Why do we build a PEX? 😄

[benjyw]

I don't know if anyone uses it. It's gigantic, and yet still doesn't run on ARM64 macos or linux.

[stuhood]

I wonder if we can (with appropriate warning) stop building the pex.

Possibly.

A PEX lockfile is effectively equivalent to a PEX. And so I think that if scie-pants were to begin consuming a released PEX lockfile to build venvs?

[thejcannon]

So do we build the PEX so that we have Pants and all its deps consistent, and in one file?

[benjyw]

I'm not sure why, and I don't think anyone consumes it these days.

[stuhood]

@benjyw , @thejcannon : I've retitled and reopened #12397: we initially thought that #7369 would resolve both that issue and #11614, but I do think that we still need to adjust the distribution model to either PEX or PyOxidizer.

[thejcannon]

I think I'm missing one step on that journey. Where does PEX come in play? Is the idea that we upload built PEXs of Pants to Releases, and then scie-pants can use that to create a venv-with-Pants?

And what do we do today? Just manually make a venv and pip install pantsbuild... into it?

[stuhood]

I think I'm missing one step on that journey. Where does PEX come in play? Is the idea that we upload built PEXs of Pants to Releases, and then scie-pants can use that to create a venv-with-Pants?

And what do we do today? Just manually make a venv and pip install pantsbuild... into it?

Correct.

[benjyw]

Or, we build pants itself as a scie?

[stuhood]

@benjyw : Yea, possibly. That still involves a PEX though: it just moves the interpreter bootstrapping out of scie-pants and into the Pants binary. I'll update the ticket to mention that possibility.