Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bias selecting the current interpreter. #783

Merged
merged 2 commits into from
Oct 27, 2019
Merged

Conversation

jsirois
Copy link
Member

@jsirois jsirois commented Oct 25, 2019

Preiously we made some effort towards this, but were not thorough.
Fix all interpreter selection logic to be both lazy and bias towards
re-using the current interpreter, only falling back to picking the
minimum version compatible interpreter from all possible compatibile
interpreters as the very last step.

Addresses item 1 in #782.

Preiously we made some effort towards this, but were not thorough.
Fix all interpreter selection logic to be both lazy and bias towards
re-using the current interpreter, only falling back to picking the
minimum version compatible interpreter from all possible compatibile
interpreters as the very last step.

Addresses item 1 in pex-tool#782.
Copy link
Collaborator

@benjyw benjyw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat!

@@ -574,7 +574,7 @@ def to_python_interpreter(full_path_or_basename):
pex_python_path = rc_variables.get('PEX_PYTHON_PATH', '')
else:
pex_python_path = ""
interpreters = find_compatible_interpreters(pex_python_path, constraints)
interpreters = list(iter_compatible_interpreters(pex_python_path, constraints))
Copy link
Collaborator

@benjyw benjyw Oct 25, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why create a list here? Wouldn't it cause the same performance problem again (albeit only a build time)? Could we do something like this?

try:
  interpreter = next(iter_compatible_interpreters(pex_python_path, constraints))
except StopIteration:
  die('Could not find compatible interpreter', CANNOT_SETUP_INTERPRETER)

Or is it specifically important to choose the min interpreter here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was just gunning for changing ~no logic and, yeah, it was only at build time so even less of a concern.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thing is, pex build time can be build tool user runtime. For example, when iterating on some tests and rebuilding the test sources chroot, this would run every time I think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would. Keep in mind two things though:

  1. The interpreters list is used below to build a multi-interpreter / multi-platform pex.
  2. There are only actually more than one interpreter if either more than one --python are passed (ie: --python=python2.7 --python=python3) or one or more --interpreter-constraint is passed.

Due to item 1, we must materialize the full list. The 1st half of item 2 is a feature, the second half of item 2 may be a bug in the ballpark of #658 and #694.

@jsirois jsirois merged commit 7d59347 into pex-tool:master Oct 27, 2019
@jsirois jsirois deleted the issues/782 branch October 27, 2019 09:21
jsirois added a commit to jsirois/pex that referenced this pull request Nov 20, 2019
Biasing interpreter selection towards the current interpreter was
implemented in pex-tool#783 but not test was added. Add a test that fails due to
a bug in path trimming logic and fix the bug.
jsirois added a commit that referenced this pull request Nov 20, 2019
Biasing interpreter selection towards the current interpreter was
implemented in #783 but not test was added. Add a test that fails due to
a bug in path trimming logic and fix the bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants