Skip to content
Browse files

Squashed commit of the following:

commit 6b07abd
Author: Eric Arellano <>
Date:   Mon Feb 25 21:49:52 2019 -0700

    Remove bad import

    My bad for not catching this before pushing.

commit 2c6fdb0
Author: Eric Arellano <>
Date:   Mon Feb 25 21:37:41 2019 -0700

    Generify solution by using compatibility_or_constraints()

    Instead of applying a bandaid for only `./pants binary`, John proposed fixing the issue with our PexBuilderWrapper itself. So, we use `compatibility_or_constrains()`, which will first try to return the target's compatibility, else will return the Python Setup subystem's value.

    The wrapper still is not ideal and John proposes killing add_interpreter_constraint() and add_interpreter_constraints_from() to instead automatically be setting the interpreter constraints from the targets graph. This PR does not make that change for the scope, but this should be noted.

commit b71f164
Author: Eric Arellano <>
Date:   Mon Feb 25 21:03:46 2019 -0700

    Fix typo

commit 3bca020
Author: Eric Arellano <>
Date:   Mon Feb 25 20:31:14 2019 -0700

    Add global interpreter constraints to Python binary creation

commit 887a8ef
Author: Eric Arellano <>
Date:   Fri Feb 22 21:05:50 2019 -0700

    Constrain to the exact Python interpreter version

    Earlier we allowed the patch version to float. We discovered in pantsbuild#7235 with the CI run that PEX was building with 2.7.10 but running with 2.7.13.

    The fix will require having Pants pass interpreter constraints to Pex. Even with that change though, the CI shard would still have the issue because the constraint would be floating.

    Now, we have the constraint be exact.
  • Loading branch information...
Eric-Arellano committed Feb 26, 2019
1 parent f530843 commit 1be9e901c5eb192c2221b9beff2043d47622213b
@@ -255,9 +255,9 @@ def add_interpreter_constraints_from(self, constraint_tgts):
# TODO this would be a great place to validate the constraints and present a good error message
# if they are incompatible because all the sources of the constraints are available.
# See:
for tgt in constraint_tgts:
for constraint in tgt.compatibility:
constraints = {self._python_setup_subsystem.compatibility_or_constraints(tgt) for tgt in constraint_tgts}
for constraint in constraints:

def add_direct_requirements(self, reqs):
for req in reqs:
@@ -141,7 +141,7 @@ def _create_binary(self, binary_tgt, results_dir):
if is_python_target(tgt):

# Add global and target-level interpreter compatibility constraints to pex info.
# Add target-level and possibly global interpreter compatibility constraints to pex info.

0 comments on commit 1be9e90

Please sign in to comment.
You can’t perform that action at this time.