IntelPython / dpnp / 42674140598

84%

Build Type

push

github

Committed by web-flow

Commit Message

Drop the unreachable default-context fallbacks in `dpnp.tensor` DLPack (#3175)

`to_dlpack_capsule` (through `get_array_dlpack_device_id`) and
`from_dlpack_capsule` in `dpnp/tensor/_dlpack.pyx` wrap
`SyclPlatform.default_context` in `try`/`except RuntimeError`, with a
fallback for a runtime that doesn't support default contexts: the export
then only rejects sub-devices, and the import uses the context of the
device's cached queue.

The fallbacks are never reached. Since dpctl 0.17.0
(IntelPython/dpctl@e53b1fde19), `SyclPlatform.default_context` raises
`dpctl.SyclContextCreationError` when the default context is
unavailable, and that class derives from `Exception`, not
`RuntimeError`. So the `except` clauses don't catch that case: the error
has gone straight to the caller in every dpctl version dpnp supports
(`dpctl>=0.20.0`). The only `RuntimeError` they could catch comes from
`SyclDevice.sycl_platform` for a device without a platform, which a
constructed `SyclDevice` never hits. Separately, DPC++ 2026.2 returns a
default context on every platform, even with
`SYCL_ENABLE_DEFAULT_CONTEXTS=0` (checked on OpenCL CPU, OpenCL GPU and
Level Zero GPU).

This PR removes `_get_default_context`, the sub-device check that only
ran on the fallback path, the `try`/`except` in `from_dlpack_capsule`,
and the cimports only that code used. DLPack export and import behave as
before: arrays not bound to the platform default context, including
those on sub-devices, are still rejected by the context check.

Cythonizing the module with Cython 3.3.1 and a syntax-only compile of
the generated C++ with icpx 2026.2 pass without warnings.

Coverage Stats

1792 of 2998 branches covered (59.77%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 1 file covered. (100.0%)

1 existing line in 1 file now uncovered.

29615 of 34204 relevant lines covered (86.58%)

39086.24 hits per line