dpnp.arange(10, dtype='i4') crashes

[oleksandr-pavlyk]

In [2]: X = dpnp.arange(10, dtype='i4')
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/home/repos/dpnp/dpnp/dpnp_utils.pyx in dpnp.dpnp_utils.checker_throw_type_error()
    112
    113 cpdef checker_throw_type_error(function_name, given_type):
--> 114     raise TypeError(f"{ERROR_PREFIX} in function {function_name}() type '{given_type}' is not supported")
    115
    116

TypeError: DPNP error: in function dpnp_dtype_to_DPNPFuncType() type 'i4' is not supported
Exception ignored in: 'dpnp.backend.dpnp_dtype_to_DPNPFuncType'
Traceback (most recent call last):
  File "dpnp/dpnp_utils.pyx", line 114, in dpnp.dpnp_utils.checker_throw_type_error
    raise TypeError(f"{ERROR_PREFIX} in function {function_name}() type '{given_type}' is not supported")
TypeError: DPNP error: in function dpnp_dtype_to_DPNPFuncType() type 'i4' is not supported
terminate called after throwing an instance of 'std::runtime_error'
  what():  DPNP Error: Function ID with unsupported first parameter type.
Aborted (core dumped)

The expected behavior is to interpret dtype='i4' as dtype=np.dtype('i4'), or at least raise an exception and not crash.

[oleksandr-pavlyk]

The exception is likely ignored in the call to cdef variant of dpnp.backend.dpnp_dtype_to_DPNPFuncType.

[shssf]

Will not be implemented.

[oleksandr-pavlyk]

The issue is not a request to implement anything. It is a bug.

The Python interpreter should never crash, or users will just stop using it.