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

Update Python rules to use the toolchain transition #12039

Closed
wants to merge 2 commits into from

Conversation

katre
Copy link
Member

@katre katre commented Sep 2, 2020

Builds on #12038, must be submitted after.

This also requires a full downstream test and probably some internal work as well.

@katre
Copy link
Member Author

katre commented Sep 2, 2020

This is phase 1 of of the switch to toolchain transitions. See bazelbuild#11584 for details.
This is phase 2 of of the switch to toolchain transitions. See bazelbuild#11584 for details.
@katre katre force-pushed the python-toolchain-transition-02 branch from 480da24 to 5057851 Compare September 11, 2020 13:05
@katre katre closed this Sep 14, 2020
@katre katre deleted the python-toolchain-transition-02 branch September 14, 2020 18:56
bazel-io pushed a commit that referenced this pull request Sep 18, 2020
This is phase 2 of of the switch to toolchain transitions. See #11584 for details.

Closes #12039.

PiperOrigin-RevId: 332441640
Yannic pushed a commit to Yannic/bazel that referenced this pull request Oct 5, 2020
This is phase 2 of of the switch to toolchain transitions. See bazelbuild#11584 for details.

Closes bazelbuild#12039.

PiperOrigin-RevId: 332441640
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.

2 participants