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
Resolve compute follows data issue in logspace and geomspace functions (#2723)
The PR closes#2352 and closes#2353.
This PR improves implementation of `dpnp.logspace` and `dpnp.geomspace`
functions based on the latest changes added to NumPy.
And it also updates logic of how input array_like arguments handled to
follow compute follows data approach.
If no `device` or `sycl_queue` keyword passed, then an array creation
function should allocate result based on input arguments (like `start`
and `stop`).
Otherwise all input arrays need to be moved to the specified queue and
resulting array must be allocated there.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,7 @@ Also, that release drops support for Python 3.9, making Python 3.10 the minimum
65
65
* Corrected a phonetic spelling issue due to incorrect using of `a nd` in docstrings [#2719](https://github.com/IntelPython/dpnp/pull/2719)
66
66
* Resolved an issue causing `dpnp.linspace` to return an incorrect output shape when inputs were passed as arrays [#2712](https://github.com/IntelPython/dpnp/pull/2712)
67
67
* Resolved an issue where `dpnp` always returns the base allocation pointer, when the view start is expected [#2651](https://github.com/IntelPython/dpnp/pull/2651)
68
+
* Fixed an issue causing an exception in `dpnp.geomspace` and `dpnp.logspace` when called with explicit `device` keyword but any input array is allocated on another device [#2723](https://github.com/IntelPython/dpnp/pull/2723)
0 commit comments