You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/array_api_stubs/_draft/creation_functions.py
+3-2
Original file line number
Diff line number
Diff line change
@@ -230,8 +230,9 @@ def from_dlpack(
230
230
device: Optional[device]
231
231
device on which to place the created array. If ``device`` is ``None`` and ``x`` supports DLPack, the output array must be on the same device as ``x``. Default: ``None``.
232
232
233
-
The v2023.12 standard only mandates that a compliant library must offer a way for ``from_dlpack`` to create an array on CPU (using
234
-
a library-specific way to represent the CPU device (``kDLCPU`` in DLPack) e.g. a ``"CPU"`` string or a ``Device("CPU")`` object).
233
+
The v2023.12 standard only mandates that a compliant library must offer a way for ``from_dlpack`` to create an array
234
+
whose underlying memory is accessible to the Python interpreter (using a library-specific way to represent the CPU
235
+
device (``kDLCPU`` in DLPack) e.g. a ``"CPU"`` string or a ``Device("CPU")`` object).
235
236
If the array library does not support the CPU device and needs to outsource to another (compliant) array library, it may do so
236
237
with a clear user documentation and/or run-time warning. If a copy must be made to enable this, and ``copy`` is set to ``False``,
0 commit comments