vispy.util.wrappers module

Some wrappers to avoid circular imports, or make certain calls easier.

The idea of a ‘global’ vispy.use function is that although vispy.app and vispy.gloo.gl can be used independently, they are not complely independent for some configureation. E.g. when using real ES 2.0, the app backend should use EGL and not a desktop OpenGL context. Also, we probably want it to be easy to configure vispy to use the ipython notebook backend, which requires specifc config of both app and gl.

This module does not have to be aware of the available app and gl backends, but it should be(come) aware of (in)compatibilities between them.

vispy.util.wrappers.run_subprocess(command, return_code=False, **kwargs)

Run command using subprocess.Popen

Run command and wait for command to complete. If the return code was zero then return, otherwise raise CalledProcessError. By default, this will also add stdout= and stderr=subproces.PIPE to the call to Popen to suppress printing to the terminal.

Parameters
commandlist of str

Command to run as subprocess (see subprocess.Popen documentation).

return_codebool

If True, the returncode will be returned, and no error checking will be performed (so this function should always return without error).

**kwargsdict

Additional kwargs to pass to subprocess.Popen.

Returns
stdoutstr

Stdout returned by the process.

stderrstr

Stderr returned by the process.

codeint

The command exit code. Only returned if return_code is True.

vispy.util.wrappers.test(*args, **kwargs)

Proxy function to delay .testing import

vispy.util.wrappers.use(app=None, gl=None)

Set the usage options for vispy

Specify what app backend and GL backend to use.

Parameters
appstr
The app backend to use (case insensitive). Standard backends:
  • ‘PyQt4’: use Qt widget toolkit via PyQt4.

  • ‘PyQt5’: use Qt widget toolkit via PyQt5.

  • ‘PyQt6’: use Qt widget toolkit via PyQt6.

  • ‘PySide’: use Qt widget toolkit via PySide.

  • ‘PySide2’: use Qt widget toolkit via PySide2.

  • ‘PySide6’: use Qt widget toolkit via PySide6.

  • ‘PyGlet’: use Pyglet backend.

  • ‘Glfw’: use Glfw backend (successor of Glut). Widely available on Linux.

  • ‘SDL2’: use SDL v2 backend.

  • ‘osmesa’: Use OSMesa backend

Additional backends:
  • ‘jupyter_rfb’: show vispy canvases in Jupyter lab/notebook (depends on the jupyter_rfb library).

glstr
The gl backend to use (case insensitive). Options are:
  • ‘gl2’: use Vispy’s desktop OpenGL API.

  • ‘pyopengl2’: use PyOpenGL’s desktop OpenGL API. Mostly for testing.

  • ‘es2’: (TO COME) use real OpenGL ES 2.0 on Windows via Angle. Availability of ES 2.0 is larger for Windows, since it relies on DirectX.

  • ‘gl+’: use the full OpenGL functionality available on your system (via PyOpenGL).

See also

vispy.app.use_app
vispy.gloo.gl.use_gl

Notes

If the app option is given, vispy.app.use_app() is called. If the gl option is given, vispy.gloo.use_gl() is called.

If an app backend name is provided, and that backend could not be loaded, an error is raised.

If no backend name is provided, Vispy will first check if the GUI toolkit corresponding to each backend is already imported, and try that backend first. If this is unsuccessful, it will try the ‘default_backend’ provided in the vispy config. If still not succesful, it will try each backend in a predetermined order.