Pex

* Plumb through the `--zip-safe`, `--always-write-cache`,
`--ignore-errors` and `--inherit-path` flags to the pex tool.
* Delete the unused `PythonDirWrapper` code.
* Split `PEXEnvironment` resolution into
`twitter.common.python.environment` and de-conflate
`WorkingSet`/`Environment` state.
* Removes the monkeypatched zipimporter in favor of keeping all eggs
unzipped within PEX files. Refactors the PEX dependency cache in
`util.py`
* Adds interpreter detection for Jython and PyPy.
* Dependency translation errors should be made uniform. (Patch
from johnsirois)
* Adds `PEX_PROFILE_ENTRIES` to limit the number of entries reported
when `PEX_PROFILE` is enabled. (Patch from rgs_)
* Bug fix: Several fixes to error handling in
`twitter.common.python.http` (From Marc Abramowitz)
* Bug fix: PEX should not always assume that `$PATH` was available.
(Patch from jamesbroadhead)
* Bug fix: Filename should be part of the .pex cache key or else
multiple identical versions will incorrectly resolve (Patch
from tc)
* Bug fix: Executed entry points shouldn't be forced to run in an
environment with `__future__` imports enabled. (Patch
from lawson_patrick)
* Bug fix: Detect versionless egg links and fail fast. (Patch from
johnsirois.)
* Bug fix: Handle setuptools>=2.1 correctly in the zipimport
monkeypatch (Patch from johnsirois.)

* Bug fix: Fix handling of Fetchers with `file://` urls.

* Adds the pex tool as a standalone tool.

* Bug fix: Bootstrapped `twitter.common.python` should declare
`twitter.common` as a namespace package.

* Make `twitter.common.python` fully standalone by consolidating
external dependencies within `twitter.common.python.common`.

* Initial published version of `twitter.common.python`.


===================
Pex Release Process
===================

.. contents:: Table of Contents

Pre-requisites
==============

PGP
---

All release tags are signed (using ``git tag --sign``) so that users of Pex can verify maintainers
have performed & trust a release. This requires releasers having a PGP key configured with git and
published to key servers. An additional nicety is to configure you PGP key with GitHub for those who
like to check provenance via a web UI.

Some documentation to help you get things set up if you don't have all of these pre-requisites:

+ Creating a key and configuring your key with Git and GitHub is all described `here <https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification>`_
+ Publishing your key to a keyserver is described `here <https://www.gnupg.org/gph/en/manual/x457.html>`_

Some key servers you probably want to publish your key to explicitly above and beyond your PGP setup's
default configured keyserver include:

+ hkps://pgp.mit.edu
+ hkps://keyserver.ubuntu.com
+ hkps://keys.openpgp.org

Preparation
===========

Version Bump and Changelog
--------------------------

Bump the version in ``pex/version.py`` and update ``CHANGES.rst``. Open a PR with these changes and
land it on https://github.com/pex-tool/pex main.

Release
=======

Push Release tag to Master
--------------------------

Sync a local branch with https://github.com/pex-tool/pex main and confirm it has the version
bump and changelog update as the tip commit:

::

$ git log --stat -1 HEAD
commit f76a3d896867a5787c151c6afe1820f14dd88848 (tag: v2.1.29, origin/main, origin/HEAD, main)
Author: John Sirois <john.siroisgmail.com>
Date: Fri Feb 5 10:24:28 2021 -0800

Prepare the 2.1.29 release. (1220)

CHANGES.rst | 19 +++++++++++++++++--
pex/version.py | 2 +-
2 files changed, 18 insertions(+), 3 deletions(-)

Tag the release and push the tag to https://github.com/pex-tool/pex main:

::