skip_backend(backend)

Within the context of a with statement, the given backend will not be called. This covers backends registered both locally and globally. Upon exit, the backend will again be considered.

Parameters

backend : {object, 'scipy'}

The backend to skip. Can either be a str containing the name of a known backend {'scipy'} or an object that implements the uarray protocol.

Context manager to skip a backend within a fixed scope.

Examples

>>> import scipy.fft as fft
... fft.fft([1])  # Calls default SciPy backend
array([1.+0.j])

This example is valid syntax, but raise an exception at execution

>>> with fft.skip_backend('scipy'):  # We explicitly skip the SciPy backend
...     fft.fft([1])                 # leaving no implementation available
Traceback (most recent call last):
    ...
BackendNotImplementedError: No selected backends had an implementation ...

See :

Back References

The following pages refer to to this document either explicitly or contain code examples using this.

scipy.fft._backend.skip_backend

Local connectivity graph

Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.

Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)

SVG is more flexible but power hungry; and does not scale well to 50 + nodes.

All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them

---

GitHub : /scipy/fft/_backend.py#159
type: <class 'function'>
Commit: