Skip to content

Commit 69430af

Browse files
authored
Remove note in adoption guidance (#306)
1 parent 45771c9 commit 69430af

File tree

1 file changed

+3
-17
lines changed

1 file changed

+3
-17
lines changed

spec/purpose_and_scope.md

Lines changed: 3 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -349,24 +349,10 @@ request a specific API version:
349349
xp = x.__array_namespace__(api_version='2020.10')
350350
```
351351

352-
```{note}
353-
354-
This is inspired by [NEP 37](https://numpy.org/neps/nep-0037-array-module.html#how-to-use-get-array-module),
355-
however it avoids adding a dependency on NumPy or having to provide a
356-
separate package just to do `get_array_module(x)`
357-
358-
NEP 37 is still in flux (it was just accepted by JAX and TensorFlow on an
359-
experimental basis), and it's possible that that should be accepted instead.
360-
361-
TBD: a decision must be made on this topic before a first version of the
362-
standard can become final. We prefer to delay this decision, to see how
363-
NEP 37 adoption will work out.
364-
```
365-
366352
The `xp` namespace must contain all functionality specified in
367-
{ref}`api-specification`. It may contain other functionality, however it is
368-
recommended not to add other functions or objects, because that may make it
369-
harder for users to write code that will work with multiple array libraries.
353+
{ref}`api-specification`. The namespace may contain other functionality; however,
354+
including additional functionality is not recommended as doing so may hinder
355+
portability and inter-operation of array libraries within user code.
370356

371357

372358
### Discoverability

0 commit comments

Comments
 (0)