Anton

Close the PR, because it was for debugging only.

@vlad-perevezentsev, it seems it's not required anymore. Feel free to close the PR.

@ndgrigorian, do we have any plans to support a list as valid indices in dpctl?

Array content can be migrated to a different device using either [dpnp.ndarray.to_device()](https://intelpython.github.io/dpnp/reference/generated/dpnp.ndarray.to_device.html) method, or by using [dpnp.asarray()](https://intelpython.github.io/dpnp/reference/generated/dpnp.asarray.html) function. The `arr.to_device(device=target_device)` method will be zero-copy if the `arr.sycl_queue` and the `dpctl.SyclQueue`...

Should that be properly clarified in the documentation? Since it might be unclear that `.shape` setter and `reshape` method behaves differently (different requirements on supported type of new shape argument)...

@icfaust, @david-cortes-intel The issue is because you have the latest dpctl installed with 2025.1 DPC++ RT package. You need to update the env to install the latest 2025.2 components.

The reason is that there is no "greater than" constraints for the DPC++ RT package in the METADATA: ```bash $ cat ./pypi_venv/lib/python3.12/site-packages/dpctl-0.20.1.dist-info/METADATA | grep Requires-Dist Requires-Dist: numpy>=1.23.0 Requires-Dist: intel-sycl-rt Requires-Dist:...

@david-cortes-intel, like mentioned in gh-1910, it's intended that they are not present in neither `requirements.txt` nor `pyproject.toml`, assuming required packages might be provided by the user (like through installing oneAPI...

For the main installation flow you are right. If you are installing dpctl from the PyPI or conda-forge, then it's requires to have a correct dependency on `intel-sycl-rt` and `intel-cmplr-lib-rt`...

> Or are you also building a binary wheel for that use-case? Yes, if I need to install that dpctl into the dev dpnp environment.