| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Some stubs still need to be modified to properly pass mypy type checking.
Also, 'device' is just left as a TypeVar() for now.
|
| |
|
|
| |
This is mostly aimed at any potential reviewers of the module for now.
|
| |
|
|
|
|
|
|
|
|
|
| |
The docstrings just point back to the functions they wrap for now. More
thought may need to be put into this for the future. Most functions can
actually perhaps inherit the docstring of the function they wrap directly, but
there are some functions that have differences (e.g., different names,
different keyword arguments, fewer keyword arguments, etc.). There's also the
question of how to handle cross-references/see alsos that point to functions
not in the API spec and behavior shown in docstring examples that isn't
required in the spec.
|
| | |
|
| |
|
|
|
|
| |
This avoids importing everything inside the individual functions, but still is
preferred over importing the functions used explicitly, as most of them clash
with the wrapper function names.
|
| | |
|
| | |
|
| |
|
|
|
| |
The specific submodule organization is an implementation detail and should not
be used. Only the top-level numpy._array_api namespace should be used.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
numpy namespace
|
| | |
|
|
|
This is based on the function stubs from the array API test suite, and is
currently based on the assumption that NumPy already follows the array API
standard. Now it needs to be modified to fix it in the places where NumPy
deviates (for example, different function names for inverse trigonometric
functions).
|