Pytest-xvfb

Latest version: v3.1.1

Safety actively analyzes 715032 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

3.1.1

------

- Same as v3.1.0, but with proper version number and fully released.

3.1.0

------

- Support for Python 3.7 and 3.8 is now dropped, while official support for
3.12 and 3.13 was added (with no code changes required).
- ``pytest.ini`` (required to run self-tests) is now included in sdists (39).
- New ``pytest_xvfb_disable`` hook to dynamically disable pytest-xvfb.

3.0.0

------

- New ``--xvfb-backend`` argument, which can be used to run Xephyr or Xvnc in
place of Xvfb (e.g. for visual inspection but on a remote system or a
consistent screen size needed).
- Support for Python 3.5 and 3.6 is now dropped, while official support for 3.9,
3.10 and 3.11 was added (with no code changes required).
- The ``Xvfb`` instance is now no longer saved in pytest's ``config`` object as
``config.xvfb`` anymore, and only available via the ``xvfb`` fixture.
- Xvfb is now shut down as late as possible (via an ``atexit`` hook registered
at import time), seemingly avoiding errors such as
"XIO: fatal IO error 0 (Success)".
- Code reformatting using black/shed.
- Packaging refresh using ``pyproject.toml``.

2.0.0

------

- PyVirtualDisplay 1.3 and newer is now supported, support for older versions
was dropped.
- Support for Python 2.7, 3.3 and 3.4 is now dropped.
- Support for Python 3.6, 3.7 and 3.8 was added (no code changes required).
- Xvfb is now not started anymore in the xdist master process.

1.2.0

------

- ``Item.get_closest_marker`` is now used, which restores compatibility with
pytest 4.1.0 and requires pytest 3.6.0 or newer.

1.1.0

------

- The ``xvfb_args`` option is now a single line parsed with ``shlex.split``.
- The ``XvfbExitedError`` exception now includes stdout and stderr.

Page 1 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.