From f36e940a4726abb38c4929259e8eaf00d68c3d18 Mon Sep 17 00:00:00 2001 From: Antony Lee Date: Tue, 29 Dec 2020 18:53:53 +0100 Subject: DOC: Avoid using "set of" when talking about an ordered list. ... or when the input isn't/cannot be a set. I left a few usages, e.g. in random sampling, where "set" is reasonable as informal description of an array as the order doesn't matter; however, for e.g. np.gradient the order of the returned list is clearly important, so "set" is wrong. Also some other minor doc edits noticed during the grepping: using `shape` instead of `form` in `cov` is consistent with most other places; the wording in `Polynomial.trim` now matches other methods on the same class. --- numpy/ma/extras.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'numpy/ma/extras.py') diff --git a/numpy/ma/extras.py b/numpy/ma/extras.py index 1bf03e966..96e64914a 100644 --- a/numpy/ma/extras.py +++ b/numpy/ma/extras.py @@ -1322,7 +1322,7 @@ def cov(x, y=None, rowvar=True, bias=False, allow_masked=True, ddof=None): observation of all those variables. Also see `rowvar` below. y : array_like, optional An additional set of variables and observations. `y` has the same - form as `x`. + shape as `x`. rowvar : bool, optional If `rowvar` is True (default), then each row represents a variable, with observations in the columns. Otherwise, the relationship -- cgit v1.2.1