Skip to content

Commit fd63c5d

Browse files
committed
Change the namespace convention to xp (borrowed from CuPy)
1 parent 8e90359 commit fd63c5d

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

spec/purpose_and_scope.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -47,11 +47,9 @@ To address both issues, a uniform method must be provided by a conforming
4747
implementation to access the API namespace, namely a function:
4848

4949
```
50-
mod = x.__array_namespace__(api_version='2020.10')
50+
xp = x.__array_namespace__(api_version='2020.10')
5151
```
5252

53-
TBD: what should the naming convention be for the namespace (`mod` above)?
54-
5553
.. note::
5654

5755
This is inspired by [NEP 37](https://numpy.org/neps/nep-0037-array-module.html#how-to-use-get-array-module),
@@ -65,7 +63,7 @@ TBD: what should the naming convention be for the namespace (`mod` above)?
6563
standard can become final. We prefer to delay this decision, to see how
6664
NEP 37 adoption will work out.
6765

68-
The `mod` namespace must contain the array object and all functionality
66+
The `xp` namespace must contain the array object and all functionality
6967
specified in :ref:`api-specification`. It may contain other functionality,
7068
however it is recommended not to add other functions or objects, because that
7169
may make it harder for users to write code that will work with multiple array

0 commit comments

Comments
 (0)