bazel-contrib / bazel-contrib/rules_python
chore: cleanup WORKSPACE
- Dominant language
- Starlark
- Stars
- 688
- Forks
- 721
- Avg merge
- 15h 7m
- Merged PRs (30d)
- 76
Description
This is a task related to eventual cleanup of WORKSPACE support. This will happen when the minimum supported version is bazel 9, that is the first version that removes the WORKSPACE support.
Q: when should that happen? I personally think that having that done when bazel 9 is released and a stable bazel version no longer has `WORKSPACE` is a good time.
The following is a list of random things that we would need to do:
- [ ] Remove entry_points in `whl_library`.
- [ ] `IS_BZLMOD_ENABLED` has to go.
- [ ] `TOOL_VERSIONS` has to probably go and we can migrate the config to `MODULE.bazel` instead.
Contributor guide
Research direction
This is a future cleanup tied to Bazel 9 and the removal of WORKSPACE support. Review the listed areas: entry_points in whl_library, IS_BZLMOD_ENABLED, TOOL_VERSIONS, and the proposed MODULE.bazel configuration. Done means resolving each checklist item once Bazel 9 is the minimum supported version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100