Skip to content

Conversation

@mattem
Copy link
Collaborator

@mattem mattem commented May 13, 2022

Fixes #19

@mattem mattem force-pushed the feat/interpreter_path branch 2 times, most recently from ec6ec3d to 9257c72 Compare May 13, 2022 16:02
@mattem mattem marked this pull request as ready for review May 13, 2022 16:03
uses_interpreter_path = True

if interpreter == None:
fail("Unable to resolve interpreter to a path or file. Ensure `interpreter` or `interpreter_file` is deifned on the py3_runtime")
Copy link
Member

Choose a reason for hiding this comment

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

When would you actually hit this? Also nit on deifned

Copy link
Member

Choose a reason for hiding this comment

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

Even if py3_toolchain.interpreter_path, is None would you not get:

interpreter = {
    path = None,
    short_path = None
}

Copy link
Member

Choose a reason for hiding this comment

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

Oh wait. If py3_toolchain.interpreter is None. Nevermind

@mattem mattem force-pushed the feat/interpreter_path branch from 9257c72 to d3cbe82 Compare May 13, 2022 17:19
@mattem mattem merged commit 9605633 into main May 13, 2022
@mattem mattem deleted the feat/interpreter_path branch May 13, 2022 17:21
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.

Handle interpreter_path on Python toolchain

4 participants