Skip to content
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

Python: 2to3 is now a write_file, not sh_binary #8187

Closed
wants to merge 3 commits into from

Conversation

laszlocsomor
Copy link
Contributor

Now py_* rules no longer depend on a sh_* rule, so
Bazel can analyze them even with
--shell_executable="".

Change-Id: I8e74d86daf385442df9e91c2dc2f7a27b7c4b236

Now py_* rules no longer depend on a sh_* rule, so
Bazel can analyze them even with
--shell_executable="".

Change-Id: I8e74d86daf385442df9e91c2dc2f7a27b7c4b236
Change-Id: I04ff5791ec135f3bf5a8d26d54674a75a7c76e25
@laszlocsomor laszlocsomor changed the title WIP: Python: 2to3 is now a write_file, not sh_binary Python: 2to3 is now a write_file, not sh_binary Apr 29, 2019
@brandjon
Copy link
Member

I'm guessing the bootstrapping failures in CI are because you need to add the new bzl file here in order for the (copied and renamed) BUILD.tools file to be usable.

Change-Id: I78057362c0f4e761362ae1d363eee9c52d3c1295
@laszlocsomor
Copy link
Contributor Author

Done. Also added an error message to the generated 2to3, pointing to #1393 (comment)

@bazel-io bazel-io closed this in c84c40d Apr 30, 2019
@laszlocsomor laszlocsomor deleted the write_xfile_2to3 branch April 30, 2019 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants