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

Error eagerly if an interpreter binary doesn't exist. #886

Merged
merged 2 commits into from Feb 13, 2020

Conversation

benjyw
Copy link
Collaborator

@benjyw benjyw commented Feb 12, 2020

The exception class already existed, it just wasn't used.

Due to caching, the interpreter may or may not fail
in find_binary(), so the calling code might fail at some
later stage.

This change causes us to fail eagerly and consistently if
the binary doesn't exist on disk.

The exception class already existed, it just wasn't used.

Due to caching, the interpreter may or may not fail
in find_binary(), so the calling code might fail at some
later stage.

This change causes us to fail eagerly and consistently if
the binary doesn't exist on disk.
@benjyw
Copy link
Collaborator Author

benjyw commented Feb 12, 2020

Fixes #672

Copy link
Contributor

@Eric-Arellano Eric-Arellano left a comment

Choose a reason for hiding this comment

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

Worth adding tests for this?

@benjyw benjyw merged commit ce0485d into pex-tool:master Feb 13, 2020
@benjyw benjyw deleted the interpreter_not_found branch February 13, 2020 03:52
@benjyw benjyw mentioned this pull request Feb 14, 2020
2 tasks
@jsirois
Copy link
Member

jsirois commented Feb 19, 2020

LGTM

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

3 participants