-
-
Notifications
You must be signed in to change notification settings - Fork 594
Merge rules_python_external #352
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
Conversation
…-from-rules-pip
…namespace_pkgs module where it really belongs
This is the beginning of making that the canonical way to get dependencies, replacing the pip features in this repo. Our plan is in multiple steps: - (this PR) bring in the repo to a subdirectory, preserving git history and contributors - clean up the code, remove mypy, get it functional in that subdirectory - add an example/integration test proving that it works - cut a patch release and get some users to test it out - communicate our deprecation plan to rules_python users - BIG SWITCH: move the rules_python_external implementation to the root, make a legacy/ directory for current impl - fill in any missing docstrings and include new rules in stardoc - cut a breaking release (a minor, since semver starting with 0. states that minors are breaking) - help users switch over - in a later breaking release, actually remove the old implementation
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
Paper trail for CLAs: this is a pure roll-forward of #348 where we had all the authors consent to their code being merged into this repo. |
8296fcf
to
ed0686c
Compare
Just enough to get CI green for now Also ignore the merge commit in git blame and the subdirectory when expanding //... pattern
ed0686c
to
1d5d724
Compare
- Clean up files that aren't needed now that it's a subdirectory of rules_python - Move the example into the top-level examples From the checklist in bazel-contrib#352 this is the third item.
- Clean up files that aren't needed now that it's a subdirectory of rules_python - Move the example into the top-level examples From the checklist in bazel-contrib#352 this is the third item.
- Clean up files that aren't needed now that it's a subdirectory of rules_python - Move the example into the top-level examples From the checklist in bazel-contrib#352 this is the third item.
- Clean up files that aren't needed now that it's a subdirectory of rules_python - Move the example into the top-level examples From the checklist in #352 this is the third item.
This is the beginning of making that the canonical way to get dependencies, replacing the pip features in this repo.
Our plan is in multiple steps:
This is a second pass at this PR since the first one got squashed