Skip to content

Commit 6f49427

Browse files
committed
DOC: update for reviewer feedback
[skip actions] [skipp cirrus] [skip azp]
1 parent 938edf0 commit 6f49427

1 file changed

Lines changed: 38 additions & 35 deletions

File tree

‎doc/neps/nep-0057-numpy-platform-support.rst‎

Lines changed: 38 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
.. _NEP47:
1+
.. _NEP57:
22

33
===============================
44
NEP 57 — NumPy platform support
@@ -10,35 +10,33 @@ NEP 57 — NumPy platform support
1010
:Created: 2026-01-30
1111
:Resolution: -
1212

13-
.. note::
14-
15-
This NEP is drafted as a policy specific to NumPy rather than a SPEC
16-
for several reasons that are all project-specific:
17-
18-
* it involves committing to a nontrivial amount of maintainer effort,
19-
* personal commitment from a maintainer may make the difference between a
20-
yes and a no of supporting a platform (e.g., NumPy supported PyPy for a
21-
long time because of the efforts of one maintainer)
22-
* support for a platform being possible at all may depend on features of the
23-
code base (e.g., NumPy supports 32-bit Python on Windows while SciPy does
24-
not because there's no suitable compiler toolchain for it)
25-
* the number of wheels depends on whether the Stable ABI can be used (NumPy
26-
is more performance-sensitive for small arrays, so can't use it)
27-
2813

2914
Abstract
3015
--------
3116

32-
This PEP documents how a platform - i.e., a specific operating system, CPU
17+
This NEP documents how a platform - i.e., a specific operating system, CPU
3318
architecture and CPython interpreter - becomes supported in NumPy, what
3419
platforms are currently supported, and were supported in the (recent) past.
3520

3621

3722
Motivation and scope
3823
--------------------
3924

40-
*This policy is being drafted now because there is a lot of interest in
41-
extending the number of platforms NumPy supports through wheels in particular.*
25+
This policy is drafted now (early 2026) because there is a lot of interest in
26+
extending the number of platforms NumPy supports through wheels in particular.
27+
It is a policy specific to NumPy - even though other projects may possibly want
28+
to refer to it - for several reasons:
29+
30+
* It involves committing to a nontrivial amount of maintainer effort,
31+
* Personal commitment from a maintainer may make the difference between a
32+
yes and a no of supporting a platform (e.g., NumPy supported PyPy for a
33+
long time because of the efforts of one maintainer)
34+
* Support for a platform being possible at all may depend on features of the
35+
code base (e.g., NumPy supports 32-bit Python on Windows while SciPy does
36+
not because there's no suitable compiler toolchain for it).
37+
* The number of wheels depends on whether the Stable ABI can be used (NumPy
38+
is more performance-sensitive for small arrays, so can't use it)
39+
4240

4341
The scope of this NEP includes:
4442

@@ -109,9 +107,10 @@ General principles
109107
`Steam Hardware & Software Survey <https://store.steampowered.com/hwsurvey/?platform=combined>`__
110108
*may have to be used.*
111109

112-
4. Adding a non-wheel CI job for a platform to the NumPy CI matrix is much
113-
cheaper, and easily reverted in case of problems. The bar for adding such
114-
jobs is low, and assessed on a case-by-case basis.
110+
4. Adding a regular CI job (i.e., not aimed at uploading wheels to PyPI) for a
111+
platform to the NumPy CI matrix is much cheaper, and easily reverted in case
112+
of problems. The bar for adding such jobs is low, and assessed on a
113+
case-by-case basis.
115114

116115
5. For all platforms in any supported tier: the relevant prerequisites in our
117116
dependencies have been met. E.g., build tools have support, and for wheels
@@ -123,11 +122,14 @@ General principles
123122
- Moving a platform to a lower support tier must be discussed on the mailing list.
124123
The circumstances for each platform are unique so the community will
125124
evaluate each proposal to demote a platform on a case-by-case basis.
126-
- Moving a platform to a higher support tier this includes releasing wheels
127-
on PyPI for that platform must be discussed on the mailing list.
128-
- Adding an entry for a platform for an unsupported platform or one without
129-
wheels can be done on GitHub, assuming it's clear from the discussion that
130-
the relevant maintainers agree.
125+
- Moving a platform to a higher support tier, if that higher tier includes
126+
releasing wheels on PyPI for that platform, must be discussed on the
127+
mailing list.
128+
- Adding an entry to a support tier in this NEP for (a) an unsupported
129+
platform or (b) a tier which does not include uploading wheels to PyPI can
130+
be done on GitHub through a regular pull request (assuming it's clear from
131+
the discussion that the relevant maintainers agree it doesn't need to hit
132+
the mailing list).
131133

132134

133135
Releasing wheels to PyPI
@@ -183,9 +185,9 @@ Tier 2
183185

184186
Tier 2 platforms:
185187

186-
- Linux x86-64 (musllinux)
187-
- Linux aarch64 (musllinux)
188-
- Free-threaded CPython
188+
- Linux x86-64 (musllinux), *Ralf Gommers*
189+
- Linux aarch64 (musllinux), *Ralf Gommers*
190+
- Free-threaded CPython, *Nathan Goldbaum, Ralf Gommers*
189191

190192

191193
Tier 3
@@ -194,16 +196,17 @@ Tier 3
194196
- Is supported as part of NumPy's regular CI setup for the ``main`` branch. CI
195197
support as defined for Tier 2.
196198
- No wheels are released on PyPI for this platform.
197-
- CI failures block releases (skips may be applied a bit more liberally).
199+
- CI failures block releases (skips may be applied when the failure is clearly
200+
platform-specific and does not indicate a regression in core functionality).
198201
- Must have at least one maintainer or a regular contributor trusted by the
199202
NumPy maintainers who commits to take responsibility for CI on the ``main``
200203
branch working.
201204

202205
Tier 3 platforms:
203206

204-
- FreeBSD (note: runs on Cirrus CI)
205-
- Linux ppc64le (note: runs on IBM-provided self-hosted runners)
206-
- Emscripten/Pyodide
207+
- FreeBSD (note: runs on Cirrus CI), *Ralf Gommers*
208+
- Linux ppc64le (note: runs on IBM-provided self-hosted runners), *Sandeep Gupta*
209+
- Emscripten/Pyodide, *Agriya Khetarpal, Gyeongjae Choi*
207210

208211

209212
Unsupported platforms
@@ -241,7 +244,7 @@ Backward compatibility
241244

242245
Moving a platform to a lower tier of support is generally backwards compatible.
243246
The exception is stopping to release wheels on PyPI for a platform. That causes
244-
signifcant disruption for existing users on that platform. Their install commands
247+
significant disruption for existing users on that platform. Their install commands
245248
(e.g., ``pip install numpy``) may stop working because if a new release no longer
246249
has wheels for the platform, by default ``pip`` will try to build from source rather
247250
than using a wheel from an older version of ``numpy``. Therefore, we should be very

0 commit comments

Comments
 (0)