Move the bazel rules for the python wrapper to MODULE.bazel #31
+131
−51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some reason using WORKSPACE makes it hard to link stim with the python wrapper -or maybe I'm just writing the wrong bazel rules- This PR moves the rules needed for the python wrapper to
MODULE.bazeland adds the rules needed to depend on pypi libraries.note that bazel deprecated
WORKSPACEand will drop support for it by the end of the year https://bazel.build/external/migration but they allow using both at the same time during migration. so thisPR starts the migration from
WORKSPACEtobzlmodpart of #17