Cleanup flags and code paths for legacy Python version api and semantics #7797
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
stale
Issues or PRs that are stale (no activity for 30 days)
team-Rules-Python
Native rules for Python
type: process
Comments
bazel-io
pushed a commit
that referenced
this issue
Mar 24, 2020
The flag now behaves as if it is always unset. It will be removed entirely in a separate CL. In the meantime, it is still disallowed to select() on the flag. Work toward #7797. RELNOTES: None PiperOrigin-RevId: 302665836
bazel-io
pushed a commit
that referenced
this issue
Mar 24, 2020
--force_python has been made a no-op, so there's no need for @bazel_tools//tools/python:python_version to consider it. Work toward #7797. RELNOTES: None PiperOrigin-RevId: 302676532
bazel-io
pushed a commit
that referenced
this issue
Mar 26, 2020
This flag enabled the new flexible Python version semantics, from the old --force_python way of doing things. It's been flipped for quite some time. This change deletes its remaining uses in tests and makes it a no-op. Work toward #7797. RELNOTES: None PiperOrigin-RevId: 303172288
bazel-io
pushed a commit
that referenced
this issue
Mar 27, 2020
This flag blocked use of the old --force_python flag, and the old default_python_version attribute. It has long since been flipped. This change deletes its uses in tests and its legacy code paths. Work toward #7797. RELNOTES: None PiperOrigin-RevId: 303229827
|
|
|
Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tracking bug for deleting
--incompatible_remove_old_python_version_api,--incompatible_allow_python_version_transitions, and the code supporting these flags.The flags are being flipped in Bazel 0.25. Google still uses these flags internally, but we expect to be migrated for them soon as well, so this might happen in the near term (O(weeks)).
Corresponds to implemented feature #6583.
The text was updated successfully, but these errors were encountered: