-
Notifications
You must be signed in to change notification settings - Fork 523
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
Flag --incompatible_python_disable_py2 will break rules_nodejs in Bazel 7.0 #3619
Comments
I think this was mis-reported; I don't see any rules_nodejs failures. |
Hi @rickeylev thanks for looking into this!
|
I see it now, thanks |
rickeylev
added a commit
to rickeylev/rules_nodejs
that referenced
this issue
Jan 30, 2023
Earlier versions have `build_tar` using `python_version=PY2`, which newer versions of Bazel will no longer support. Fixes bazel-contrib#3619
3 tasks
alexeagle
pushed a commit
that referenced
this issue
Jan 31, 2023
Earlier versions have `build_tar` using `python_version=PY2`, which newer versions of Bazel will no longer support. Fixes #3619
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Incompatible flag
--incompatible_python_disable_py2
will be enabled by default in the next major release (Bazel 7.0), thus breaking rules_nodejs. Please migrate to fix this and unblock the flip of this flag.The flag is documented here: bazelbuild/bazel#17293.
Please check the following CI builds for build and test results:
Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.
The text was updated successfully, but these errors were encountered: