-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Write a Tutorial for Python and Bazel #64
Comments
Also, should we use https://bazel.build/build/bzlmod in the demo? We had a question on the call: "What are you doing for bazel 6?" And I know that bzlmod is one of the key differences" |
Great question. I don't have a good sense for how long it will take folks to transition to bzlmod. My initial thought is that we should write the tutorial to use 5.3.1. All of the tutorials will need to be updated at some point to support Bazel 6.0. |
Bazel 7 will have bzlmod enabled by default, so if the SIG wants to fund this work, I think it's the right time now. Also @rickeylev indicated in an email to me that the rules_python bzlmod API surface is "stable enough" to rely on it for example code outside the repo that would accompany a tutorial. Even though we put the content for the Go tutorial on the SIG GHPages site, we never added any further content like this. I think https://bazel.build/start is probably the better place for the content to live, assuming we have a Googler committed to help review and land the commits. If so, then https://github.com/bazelbuild/examples is probably the repository where any code samples for the tutorial ought to go, as that's where the other language tutorials on https://bazel.build/start point. |
@alexeagle happy to start on this. We need to update the Golang example as well. |
For Go see bazel-contrib/rules_go#3717 |
Write a tutorial for https://github.com/bazelbuild/rules_python. We can base the tutorial on demo code in the rules_python repository.
@cgrindel please assign this to me.
The text was updated successfully, but these errors were encountered: