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

feat: enable rules_python Starlark implemention by default for Bazel 7+ #1699

Merged
merged 3 commits into from
Feb 13, 2024

Conversation

rickeylev
Copy link
Collaborator

@rickeylev rickeylev commented Jan 17, 2024

This makes the base rules use the Starlark code in rules_python
("pystar") instead of what is built into Bazel 7.

The pystar implementation can be disabled by setting
RULES_PYTHON_ENABLE_PYSTAR=0 in your environment or using
--action_env.

Earlier versions of Bazel continue to use the rules built into Bazel
regardless (the new implementation requires special APIs that only Bazel
7 has).

Work towards #1069

@rickeylev rickeylev force-pushed the pystar.enabled.by.default branch 2 times, most recently from e7481b1 to 779f050 Compare January 21, 2024 07:13
This makes the base rules use the Starlark code in rules_python
("pystar") instead of what is built into Bazel 7.

The pystar implementation can be disabled by setting
`RULES_PYTHON_ENABLE_PYSTAR=0` in your environment or using
`--action_env`.

Earlier versions of Bazel continue to use the rules built into Bazel
regardless (the new implementation requires special APIs that only Bazel
7 has).

Work towards bazelbuild#1069
@rickeylev rickeylev force-pushed the pystar.enabled.by.default branch from 779f050 to c0880bf Compare January 23, 2024 00:21
@rickeylev rickeylev requested a review from aignas January 23, 2024 00:24
@rickeylev rickeylev marked this pull request as ready for review January 23, 2024 00:24
@rickeylev
Copy link
Collaborator Author

Doh, forgot the changelog entry

@rickeylev
Copy link
Collaborator Author

posterity, from maintainer's meeting:

The plan for this PR is to make it its own release. So immediately after the next release, I'll merge this and then do a subsequent release. This is to help decouple it from the other fixes/features/breaking-changes that have been going in. I'm not too worried about regressions (Bazel 7 uses the new starlark impl this is based upon; Google has been using the starlark impl for many months and the rules_python variant for several weeks), but I'd rather be more cautious in this particular case.

@rickeylev rickeylev added this pull request to the merge queue Feb 13, 2024
Merged via the queue into bazelbuild:main with commit 5cd32ad Feb 13, 2024
4 checks passed
@rickeylev rickeylev deleted the pystar.enabled.by.default branch February 13, 2024 04:32
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