-
Notifications
You must be signed in to change notification settings - Fork 321
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
rules_mypy@0.1.0 #2545
rules_mypy@0.1.0 #2545
Conversation
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (rules_mypy) have been updated in this PR. Please review the changes. |
@Wyverald I'm a little stumped on the CI error here -- this works for me locally on a mac and using GitHub runners, Python 3.12 is set using rules_python in the ruleset. Any suggestions? |
I can repro this, but have no idea how to debug it. Try doing exactly what BCR's presubmit is doing and see if it repros for you: mkdir -p ~/bcr
cd ~/bcr
git clone https://github.com/bazelbuild/bazel-central-registry .
git fetch origin refs/pull/2545/head
git checkout FETCH_HEAD
mkdir -p ~/test
cd ~/test
echo "bazel_dep(name='rules_mypy', version='0.1.0')" > MODULE.bazel
echo "common --registry=file://$HOME/bcr/" > .bazelrc
bazel build @rules_mypy//... |
Re: bazelbuild/rules_python#1824 and the BCR failure in bazelbuild/bazel-central-registry#2545
It looks like I ran into bazelbuild/rules_python#1824. After pinning a specific py_binary version I was able to successfully build from a repo tgz the same way BCR does. |
Feel free to close this one out. |
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.
Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.
Pull request was closed
Release: https://github.com/theoremlp/rules_mypy/releases/tag/v0.1.0
Automated by Publish to BCR