diff options
| -rw-r--r-- | doc/neps/_static/nep-0000.png | bin | 20813 -> 12925 bytes | |||
| -rw-r--r-- | doc/neps/index.rst.tmpl | 38 | ||||
| -rw-r--r-- | doc/neps/nep-0000.rst | 14 | ||||
| -rw-r--r-- | doc/neps/nep-0016-abstract-array.rst | 2 | ||||
| -rw-r--r-- | doc/neps/nep-0018-array-function-protocol.rst | 2 | ||||
| -rw-r--r-- | doc/neps/nep-0022-ndarray-duck-typing-overview.rst | 2 |
6 files changed, 37 insertions, 21 deletions
diff --git a/doc/neps/_static/nep-0000.png b/doc/neps/_static/nep-0000.png Binary files differindex 51eb2b258..0fc8176d2 100644 --- a/doc/neps/_static/nep-0000.png +++ b/doc/neps/_static/nep-0000.png diff --git a/doc/neps/index.rst.tmpl b/doc/neps/index.rst.tmpl index bf4df3dfb..0ad8e0f80 100644 --- a/doc/neps/index.rst.tmpl +++ b/doc/neps/index.rst.tmpl @@ -29,8 +29,19 @@ Meta-NEPs (NEPs about NEPs or Processes) nep-template -Accepted NEPs, implementation in progress ------------------------------------------ +Provisional NEPs (provisionally accepted; interface may change) +--------------------------------------------------------------- + +.. toctree:: + :maxdepth: 1 + +{% for nep, tags in neps.items() if tags['Status'] == 'Provisional' %} + {{ tags['Title'] }} <{{ tags['Filename'] }}> +{% endfor %} + + +Accepted NEPs (implementation in progress) +------------------------------------------ .. toctree:: :maxdepth: 1 @@ -52,7 +63,7 @@ Open NEPs (under consideration) -Implemented NEPs +Finished NEPs ---------------- .. toctree:: @@ -62,32 +73,23 @@ Implemented NEPs {{ tags['Title'] }} <{{ tags['Filename'] }}> {% endfor %} -Deferred NEPs -------------- +Deferred and Superseded NEPs +---------------------------- .. toctree:: :maxdepth: 1 -{% for nep, tags in neps.items() if tags['Status'] == 'Deferred' %} +{% for nep, tags in neps.items() if tags['Status'] in ('Deferred', 'Superseded') %} {{ tags['Title'] }} <{{ tags['Filename'] }}> {% endfor %} -Rejected NEPs -------------- +Rejected and Withdrawn NEPs +--------------------------- .. toctree:: :maxdepth: 1 -{% for nep, tags in neps.items() if tags['Status'] == 'Rejected' %} +{% for nep, tags in neps.items() if tags['Status'] in ('Rejected', 'Withdrawn') %} {{ tags['Title'] }} <{{ tags['Filename'] }}> {% endfor %} -Withdrawn NEPs --------------- - -.. toctree:: - :maxdepth: 1 - -{% for nep, tags in neps.items() if tags['Status'] == 'Withdrawn' %} - {{ tags['Title'] }} <{{ tags['Filename'] }}> -{% endfor %} diff --git a/doc/neps/nep-0000.rst b/doc/neps/nep-0000.rst index 5e719b0f9..89ba177cb 100644 --- a/doc/neps/nep-0000.rst +++ b/doc/neps/nep-0000.rst @@ -111,6 +111,20 @@ Once a NEP has been ``Accepted``, the reference implementation must be completed. When the reference implementation is complete and incorporated into the main source code repository, the status will be changed to ``Final``. +To allow gathering of additional design and interface feedback before +committing to long term stability for a language feature or standard library +API, a NEP may also be marked as "Provisional". This is short for +"Provisionally Accepted", and indicates that the proposal has been accepted for +inclusion in the reference implementation, but additional user feedback is +needed before the full design can be considered "Final". Unlike regular +accepted NEPs, provisionally accepted NEPs may still be Rejected or Withdrawn +even after the related changes have been included in a Python release. + +Wherever possible, it is considered preferable to reduce the scope of a +proposal to avoid the need to rely on the "Provisional" status (e.g. by +deferring some features to later NEPs), as this status can lead to version +compatibility challenges in the wider NumPy ecosystem. + A NEP can also be assigned status ``Deferred``. The NEP author or a core developer can assign the NEP this status when no progress is being made on the NEP. diff --git a/doc/neps/nep-0016-abstract-array.rst b/doc/neps/nep-0016-abstract-array.rst index 0dc201541..86d164d8e 100644 --- a/doc/neps/nep-0016-abstract-array.rst +++ b/doc/neps/nep-0016-abstract-array.rst @@ -12,7 +12,7 @@ NEP 16 — An abstract base class for identifying "duck arrays" This NEP has been withdrawn in favor of the protocol based approach described in - `NEP 22 <http://www.numpy.org/neps/nep-0022-ndarray-duck-typing-overview.html>`__ + `NEP 22 <nep-0022-ndarray-duck-typing-overview.html>`__ Abstract -------- diff --git a/doc/neps/nep-0018-array-function-protocol.rst b/doc/neps/nep-0018-array-function-protocol.rst index 4e0fee384..75f4132a4 100644 --- a/doc/neps/nep-0018-array-function-protocol.rst +++ b/doc/neps/nep-0018-array-function-protocol.rst @@ -7,7 +7,7 @@ NEP 18 — A dispatch mechanism for NumPy's high level array functions :Author: Marten van Kerkwijk <mhvk@astro.utoronto.ca> :Author: Hameer Abbasi <hameerabbasi@yahoo.com> :Author: Eric Wieser <wieser.eric@gmail.com> -:Status: Accepted +:Status: Provisional :Type: Standards Track :Created: 2018-05-29 :Resolution: https://mail.python.org/pipermail/numpy-discussion/2018-August/078493.html diff --git a/doc/neps/nep-0022-ndarray-duck-typing-overview.rst b/doc/neps/nep-0022-ndarray-duck-typing-overview.rst index 480da51a3..077166453 100644 --- a/doc/neps/nep-0022-ndarray-duck-typing-overview.rst +++ b/doc/neps/nep-0022-ndarray-duck-typing-overview.rst @@ -3,7 +3,7 @@ NEP 22 — Duck typing for NumPy arrays – high level overview =========================================================== :Author: Stephan Hoyer <shoyer@google.com>, Nathaniel J. Smith <njs@pobox.com> -:Status: Accepted +:Status: Final :Type: Informational :Created: 2018-03-22 :Resolution: https://mail.python.org/pipermail/numpy-discussion/2018-September/078752.html |
