-
Notifications
You must be signed in to change notification settings - Fork 9
feat: provide default deps #13
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
base: main
Are you sure you want to change the base?
Conversation
Note, I actually need this to stamp out an aspect_rules_py#py_test so that debugging works in the editor. Maybe I'll just port your macro into our ruleset - would you be okay with that @caseyduquettesc ? |
Comes from caseyduquettesc/rules_python_pytest#13 It's much easier to properly gazelle-generate a BUILD file in this shape rather than the awkward way you're forced to hold our py_pytest_main.
For sure. Not sure what license is in here, but feel free to contribute or copy or simply make it obsolete! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this improvement. Big QoL win!
@caseyduquettesc needs fresh approve to trigger tests again |
For next steps - let's make some more improvements here so I'm not in the loop on aspect-build/rules_py#401 |
I shouldn't have committed changes to MODULE.bazel.lock, could you bump CI again? |
Comes from caseyduquettesc/rules_python_pytest#13 It's much easier to properly gazelle-generate a BUILD file in this shape rather than the awkward way you're forced to hold our py_pytest_main.
Alternative to #10 which I think is less brittle and follows practices we learned in many other rulesets.
Tested by inserting this into a repo generated with
aspect init
(I'm working to polish up https://github.com/aspect-build/aspect-workflows-template so developers never need to touch BUILD files)