Now
MAIN commitmail json YAML
pkgsrc/devel/py-test-benchmark/Makefile@1.3
/
diff
pkgsrc/devel/py-test-benchmark/distinfo@1.2 / diff
pkgsrc/devel/py-test-benchmark/distinfo@1.2 / diff
py-test-benchmark: updated to 3.4.1
3.4.1 (2021-04-17)
------------------
* 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 (2021-04-17)
------------------
* Disable progress indication unless ``--benchmark-verbose`` is used.
* Added Python 3.9, dropped Python 3.5.
* 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.
* ``PerformanceRegression`` exception no longer inherits ``pytest.UsageError`` (apparently a *final* class).
3.4.1 (2021-04-17)
------------------
* 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 (2021-04-17)
------------------
* Disable progress indication unless ``--benchmark-verbose`` is used.
* Added Python 3.9, dropped Python 3.5.
* 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.
* ``PerformanceRegression`` exception no longer inherits ``pytest.UsageError`` (apparently a *final* class).