You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only available example that uses rules_py is within the rules_py repository. Hence the WORKSPACE and BUILD files contain more than what is necessary to just use the rules.
Describe the feature
A simple stand-alone repository, e.g. https://github.com/aspect-build/bazel-examples/tree/main/rules_py/, that contains a minimal application (e.g. one library, one executable), that uses rules_py to define those. It should have at least one external dependency. This should enable users that want to use rules_py to start a project by adapting the given example.
we now have aspect init in our CLI which creates a new minimal rules_py project. I think that's as good as a standalone example. You can look in https://github.com/aspect-build/aspect-workflows-template for the scaffold that's used to stamp out a new project.
What is the current behavior?
The only available example that uses rules_py is within the
rules_py
repository. Hence the WORKSPACE and BUILD files contain more than what is necessary to just use the rules.Describe the feature
A simple stand-alone repository, e.g.
https://github.com/aspect-build/bazel-examples/tree/main/rules_py/
, that contains a minimal application (e.g. one library, one executable), that usesrules_py
to define those. It should have at least one external dependency. This should enable users that want to userules_py
to start a project by adapting the given example.https://github.com/aspect-build/bazel-examples/tree/main/oci_python_image is already quite close, but comes bundled with docker, which adds some more complexity.
The text was updated successfully, but these errors were encountered: