summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas A Caswell <tcaswell@gmail.com>2019-07-24 18:46:16 -0400
committerGitHub <noreply@github.com>2019-07-24 18:46:16 -0400
commitca3292df13f96437962ff864adf3b0cb98e5d5fd (patch)
treea4a740774bdf31836353e3bd96bca82295339e6b
parentffd49776c5539f27f7de547c59769420e3986020 (diff)
downloadnumpy-ca3292df13f96437962ff864adf3b0cb98e5d5fd.tar.gz
Adopt wording tweaks from @ericdill
Co-Authored-By: Eric Dill <ericdill@users.noreply.github.com>
-rw-r--r--doc/neps/nep-0029-deprecation_policy.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/neps/nep-0029-deprecation_policy.rst b/doc/neps/nep-0029-deprecation_policy.rst
index 06203ab02..803042d6d 100644
--- a/doc/neps/nep-0029-deprecation_policy.rst
+++ b/doc/neps/nep-0029-deprecation_policy.rst
@@ -123,7 +123,7 @@ the minimum version of Python supported. While this is a notionally
simple policy, it makes it hard for downstream users to predict what
the future minimum versions will be. As there is no objective threshold
to when the minimum version should be dropped, it is easy for these
-discussions to devolve into bike shedding and acrimony.
+discussions to devolve into [bike shedding](https://en.wikipedia.org/wiki/Wikipedia:Avoid_Parkinson%27s_bicycle-shed_effect) and acrimony.
All Python Software Foundation supported versions
@@ -145,7 +145,7 @@ packages to carry fewer version-specific patches.
Default version on Linux distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The policy could be support the version of Python that ships by
+The policy could be to support the version of Python that ships by
default in the latest Ubuntu LTS or CentOS/RHEL release. However, we
would still have to standardize across the community which
distribution we are following.