| commit | 42136e1d931722e87377da6a403c34730f21e346 | [log] [tgz] |
|---|---|---|
| author | Travis Clarke <travis.m.clarke@gmail.com> | Mon Aug 05 07:43:50 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 05 07:44:54 2019 -0700 |
| tree | cfd00cec82ce363810caada113ff782848050b44 | |
| parent | 338829f2633e91ae0492ee4169446465e10b5994 [diff] |
update docs to reflect new default "python_version" Since [0.25.0](https://github.com/bazelbuild/bazel/blob/master/CHANGELOG.md#release-0250-2019-05-01) (commit: 33e571939085dd158422e1b3503cfc738e0a3165), the default `python_version` for python rules is `"PY3"`, yet the docs still indicate that it is `"PY2"`. This is an update to make it more clear. Closes #9020. PiperOrigin-RevId: 261682822
diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java index 25d2bc8..90ddd89 100644 --- a/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java +++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java
@@ -180,7 +180,7 @@ + " to the configuration")) /* <!-- #BLAZE_RULE($base_py_binary).ATTRIBUTE(python_version) --> Whether to build this target (and its transitive <code>deps</code>) for Python 2 or Python - 3. Valid values are <code>"PY2"</code> (the default) and <code>"PY3"</code>. + 3. Valid values are <code>"PY2"</code> and <code>"PY3"</code> (the default). <p>Under the old semantics (<code>--incompatible_allow_python_version_transitions=false</code>), the Python version