Skip to content
This repository was archived by the owner on Jan 8, 2024. It is now read-only.

Fixes for --all_incompatible_changes - #96

Merged
brandjon merged 2 commits into
masterfrom
pyincompat
Mar 7, 2019
Merged

Fixes for --all_incompatible_changes#96
brandjon merged 2 commits into
masterfrom
pyincompat

Conversation

@brandjon

@brandjon brandjon commented Mar 7, 2019

Copy link
Copy Markdown
Contributor

This gets bazel build //... --all_incompatible_changes working with Bazel 0.23.

("Diffbased" on #95, but I don't know what the equivalent of diffbase is in github if any. Just ignore the docgen commit in this PR.)

Edit: To confirm and save you some time, the content of this PR is just 2 changed lines.

@brandjon
brandjon requested a review from gpshead March 7, 2019 19:42
@brandjon

brandjon commented Mar 7, 2019

Copy link
Copy Markdown
Contributor Author

(x-ref bazelbuild/bazel#7308 and bazelbuild/bazel#7347)

@gpshead

gpshead commented Mar 7, 2019

Copy link
Copy Markdown

The equivalent of a diffbase is using a new branch for every PR. I don't believe GH has a way to deal with chained PRs other than doing them as PR reviews within a fork before finally merging them all to the main dest repo?

brandjon added 2 commits March 7, 2019 17:12
This is a one-liner to rename `default_python_version` for a `py_binary` target.

This does not rename the corresponding attribute on the `parfile` rule. That attribute is currently marked mandatory, though it doesn't appear to be used. If we want to keep it, and if we want a gentle migration period, we'd need to introduce a new `python_version` attribute for `parfile`, make them both non-mandatory, and validate them at anaylsis time, similarly to how Bazel handled the rename of this attribute for `py_binary`/`py_test`.
@brandjon
brandjon merged commit 0356bef into master Mar 7, 2019
@brandjon
brandjon deleted the pyincompat branch May 13, 2019 16:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants