Skip to content

Commit 0e5fbac

Browse files
MAINT: Fix a few typos - and sometimes improve wording
1 parent d6bfeb0 commit 0e5fbac

File tree

12 files changed

+14
-14
lines changed

12 files changed

+14
-14
lines changed

.github/workflows/linux_simd.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ name: Linux SIMD tests
1717
#
1818
# - native:
1919
# Tests against the host CPU features set as the baseline without enabling any runtime dispatched features.
20-
# Intended to assess the entire NumPy codebase against host flags, even for code sections lacking handwritten SIMD intrincis.
20+
# Intended to assess the entire NumPy codebase against host flags, even for code sections lacking handwritten SIMD intrinsics.
2121
#
2222
# - without_avx512/avx2/fma3:
2323
# Uses runtime SIMD dispatching but disables AVX2, FMA3, and AVX512.

doc/release/upcoming_changes/27156.change.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ NEP 50 promotion state option removed
33
The NEP 50 promotion state settings are now removed. They were always
44
meant as temporary means for testing.
55
A warning will be given if the environment variable is set to anything
6-
but ``NPY_PROMOTION_STATE=weak`` wile ``_set_promotion_state``
6+
but ``NPY_PROMOTION_STATE=weak`` while ``_set_promotion_state``
77
and ``_get_promotion_state`` are removed.
88
In case code used ``_no_nep50_warning``, a ``contextlib.nullcontext``
99
could be used to replace it when not available.

doc/source/building/cross_compilation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ may need to pass to Meson to successfully cross compile.
2424

2525
One possible hiccup is that the build requires running a compiled executable in
2626
order to determine the ``long double`` format for the host platform. This may be
27-
an obstable, since it requires ``crossenv`` or QEMU to run the host (cross)
27+
an obstacle, since it requires ``crossenv`` or QEMU to run the host (cross)
2828
Python. To avoid this problem, specify the paths to the relevant directories in
2929
your *cross file*:
3030

doc/source/user/how-to-io.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -343,6 +343,6 @@ storage.
343343

344344
>>> import os
345345
>>> # list all files created in testsetup. If needed there are
346-
>>> # convenienes in e.g. astroquery to do this more automatically
346+
>>> # conveniences in e.g. astroquery to do this more automatically
347347
>>> for filename in ['csv.txt', 'fixedwidth.txt', 'nan.txt', 'skip.txt', 'tabs.txt']:
348348
... os.remove(filename)

meson_cpu/main_config.h.in

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
*/
1212
#ifndef @P@_CPU_DISPATCHER_CONF_H_
1313
#define @P@_CPU_DISPATCHER_CONF_H_
14-
/// This definition is required to provides comptablity with NumPy distutils
14+
/// This definition is required to provide comptibility with NumPy distutils
1515
#define @P@_CPU_MESON_BUILD
1616
/**
1717
* @def @P@WITH_CPU_BASELINE

numpy/_core/src/multiarray/buffer.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
/*************************************************************************
2727
* PEP 3118 buffer protocol
2828
*
29-
* Implementing PEP 3118 is somewhat convoluted because of the desirata:
29+
* Implementing PEP 3118 is somewhat convoluted because of the requirements:
3030
*
3131
* - Don't add new members to ndarray or descr structs, to preserve binary
3232
* compatibility. (Also, adding the items is actually not very useful,

numpy/_core/tests/test_custom_dtypes.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ def test_possible_and_impossible_reduce(self):
116116
# For reductions to work, the first and last operand must have the
117117
# same dtype. For this parametric DType that is not necessarily true.
118118
a = self._get_array(2.)
119-
# Addition reductin works (as of writing requires to pass initial
119+
# Addition reduction works (as of writing requires to pass initial
120120
# because setting a scaled-float from the default `0` fails).
121121
res = np.add.reduce(a, initial=0.)
122122
assert res == a.astype(np.float64).sum()

numpy/_core/tests/test_numeric.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2179,9 +2179,9 @@ class TestArrayComparisons:
21792179
)
21802180
def test_array_equal_equal_nan(self, bx, by, equal_nan, expected):
21812181
"""
2182-
This test array_equal for a few combinaison:
2182+
This test array_equal for a few combinations:
21832183
2184-
- are the two inputs the same object or not (same object many not
2184+
- are the two inputs the same object or not (same object may not
21852185
be equal if contains NaNs)
21862186
- Whether we should consider or not, NaNs, being equal.
21872187

numpy/_core/tests/test_ufunc.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2544,8 +2544,8 @@ def test_reducelike_out_promotes(self):
25442544
assert single_res != res
25452545

25462546
def test_reducelike_output_needs_identical_cast(self):
2547-
# Checks the case where the we have a simple byte-swap works, maily
2548-
# tests that this is not rejected directly.
2547+
# Checks the case where a simple byte-swap works, mainly tests that
2548+
# this is not rejected directly.
25492549
# (interesting because we require descriptor identity in reducelikes).
25502550
arr = np.ones(20, dtype="f8")
25512551
out = np.empty((), dtype=arr.dtype.newbyteorder())

numpy/f2py/tests/test_array_from_pyobj.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ def is_intent_exact(self, *names):
143143

144144
# 32 bit system malloc typically does not provide the alignment required by
145145
# 16 byte long double types this means the inout intent cannot be satisfied
146-
# and several tests fail as the alignment flag can be randomly true or fals
146+
# and several tests fail as the alignment flag can be randomly true or false
147147
# when numpy gains an aligned allocator the tests could be enabled again
148148
#
149149
# Furthermore, on macOS ARM64, LONGDOUBLE is an alias for DOUBLE.

0 commit comments

Comments
 (0)