Skip to content
This repository was archived by the owner on May 3, 2023. It is now read-only.

Update pytest-benchmark to 4.0.0#207

Open
pyup-bot wants to merge 2 commits intomainfrom
pyup-update-pytest-benchmark-3.2.3-to-4.0.0
Open

Update pytest-benchmark to 4.0.0#207
pyup-bot wants to merge 2 commits intomainfrom
pyup-update-pytest-benchmark-3.2.3-to-4.0.0

Conversation

@pyup-bot
Copy link
Copy Markdown
Collaborator

This PR updates pytest-benchmark from 3.2.3 to 4.0.0.

Changelog

4.0.0

------------------

* Dropped support for legacy Pythons (2.7, 3.6 or older).
* Switched CI to GitHub Actions.
* Removed dependency on the ``py`` library (that was not properly specified as a dependency anyway).
* Fix skipping test in `test_utils.py` if appropriate VCS not available. Also fix typo.
Contributed by Sam James in `211 <https://github.com/ionelmc/pytest-benchmark/pull/211>`_.
* Added support for pytest 7.2.0 by using ``pytest.hookimpl`` and ``pytest.hookspec`` to configure hooks.
Contributed by Florian Bruhin in `224 <https://github.com/ionelmc/pytest-benchmark/pull/224>`_.
* Now no save is attempted if ``--benchmark-disable`` is used.
Fixes `205 <https://github.com/ionelmc/pytest-benchmark/issues/205>`_.
Contributed by Friedrich Delgado in `207 <https://github.com/ionelmc/pytest-benchmark/pull/207>`_.

3.4.1

------------------

* Republished with updated changelog.

I intended to publish a ``3.3.0`` release but I messed it up because bumpversion doesn't work well with pre-commit
apparently... thus ``3.4.0`` was set in by accident.

3.4.0

------------------

* Disable progress indication unless ``--benchmark-verbose`` is used.
Contributed by Dimitris Rozakis in `149 <https://github.com/ionelmc/pytest-benchmark/pull/149>`_.
* Added Python 3.9, dropped Python 3.5.
Contributed by Miroslav Šedivý in `189 <https://github.com/ionelmc/pytest-benchmark/pull/189>`_.
* Changed the "cpu" data in the json output to include everything that cpuinfo outputs, for better or worse as cpuinfo 6.0 changed some
fields. Users should now ensure they are an adequate cpuinfo package installed.
**MAY BE BACKWARDS INCOMPATIBLE**
* Changed behavior of ``--benchmark-skip`` and ``--benchmark-only`` to apply early in the collection phase.
This means skipped tests won't make pytest run fixtures for said tests unnecessarily, but unfortunately this also means
the skipping behavior will be applied to any tests that requires a "benchmark" fixture, regardless if it would come from pytest-benchmark
or not.
**MAY BE BACKWARDS INCOMPATIBLE**
* Added ``--benchmark-quiet`` - option to disable reporting and other information output.
* Squelched unnecessary warning when ``--benchmark-disable`` and save options are used.
Fixes `199 <https://github.com/ionelmc/pytest-benchmark/issues/199>`_.
* ``PerformanceRegression`` exception no longer inherits ``pytest.UsageError`` (apparently a *final* class).
Links

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant