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

refactor(toolchains): split the implementation of toolchain rules to separate files #2232

Merged

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Sep 19, 2024

This makes the dependency management in WORKSPACE much easier to do.

Summary:

  • refactor: split out the py_repositories call to a separate file
  • refactor: split out the python_repository rule to a separate file
  • refactor: split out the standalone interpreter utility function
  • refactor: split out the python_register_toolchains function
  • refactor: rename the remaining file

Work towards #2081.

Comment on lines +22 to +23
def is_standalone_interpreter(rctx, python_interpreter_path, *, logger = None):
"""Query a python interpreter target for whether or not it's a rules_rust provided toolchain
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you happen to know the history of this function? It's always struck me as a bit strange.

@rickeylev rickeylev added this pull request to the merge queue Sep 19, 2024
Merged via the queue into bazelbuild:main with commit ade0b2b Sep 19, 2024
4 checks passed
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.

2 participants