Skip to content

docs: Better explain when and how to use toolchains for bzlmod - #1349

Merged
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:readme.updates
Jul 31, 2023
Merged

docs: Better explain when and how to use toolchains for bzlmod#1349
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:readme.updates

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

This explains the different ways to register toolchains and how to use them.

Also fixes python_aliases -> python_versions repo name

This explains the different ways to register toolchains and how to use
them.

Also fixes python_aliases -> python_versions repo name

@aignas aignas left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks for this explanation, I think it becomes much clearer of what is possible and how the toolchains can be used.

That said, I wonder if if we should advise users to only use X.Y instead of X.Y.Z in the python_version field. All of the docs only have examples in that case and I am wondering if saying python_version = "3.11.1" even makes sense here.

@rickeylev

rickeylev commented Jul 30, 2023 via email

Copy link
Copy Markdown
Collaborator Author

@rickeylev

Copy link
Copy Markdown
Collaborator Author

Updated the attribute docs for the python_version attributes.

@rickeylev
rickeylev requested a review from Solumin July 31, 2023 20:31
@rickeylev
rickeylev added this pull request to the merge queue Jul 31, 2023
Merged via the queue into bazel-contrib:main with commit e355bec Jul 31, 2023
@rickeylev
rickeylev deleted the readme.updates branch October 24, 2023 18:52
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.

3 participants