devel/py-pytest-cases 3.10.1

devel/py-pytest-cases: Update to 3.10.1

Changes:	https://github.com/smarie/python-pytest-cases/releases
		https://smarie.github.io/python-pytest-cases/changelog/

devel/py-pytest-cases: Update to 3.9.1

Changes:	https://github.com/smarie/python-pytest-cases/releases
		https://smarie.github.io/python-pytest-cases/changelog/

devel/py-pytest-cases: Add py-pytest-cases 3.8.6

Did you ever think that most of your test functions were actually the same test
code, but with different data inputs and expected results/exceptions?
- pytest-cases leverages pytest and its great @pytest.mark.parametrize
  decorator, so that you can separate your test cases from your test functions.
- In addition, pytest-cases provides several useful goodies to empower pytest.
  In particular it improves the fixture mechanism to support "fixture unions".
  This is a major change in the internal pytest engine, unlocking many
  possibilities such as using fixture references as parameter values in a test
  function. See here.

pytest-cases is fully compliant with pytest-harvest so you can easily monitor
the execution times and created artifacts. With it, it becomes very easy to
create a complete data science benchmark, for example comparing various models
on various datasets.

devel/py-pytest-cases: Remove expired port

2025-06-01 devel/py-pytest-cases: Depends on expired devel/py-makefun

devel/py-pytest-cases: Update to 3.8.6

Changes:	https://github.com/smarie/python-pytest-cases/releases

all: expire (indirect) consumers of devel/py-makefun on 2025-06-01

devel/py-setuptools-scm: update to 8.0.4

Directory and PORTNAME changed to match normalised name in release
tarball; consumers updated to match.

Although setuptools itself is specified as a run dependency in the
Python package metadata, it is currently left out here to prevent
environment pollution until at least PR 270510 is committed.
Additionally, this version of setuptools-scm requires setuptools>=61,
which means this version is only meant for USE_PYTHON=pep517 ports
as all USE_PYTHON=distutils ports will switch to devel/py-setuptools58
also after PR 270510. science/py-emmet-core is switched to
devel/py-setuptools_scm7 accordingly, as it specifies setuptools-scm<8.
devel/py-{flit-scm,hatch-vcs} have ${PY_SETUPTOOLS} added to
RUN_DEPENDS to compensate.

Further details: https://wiki.freebsd.org/Python/setuptools

Reported by: yuri
Co-authored by: matthew
Exp-run by: antoine (earlier iteration)
Approved by: yuri (science/py-emmet-core, previous iteration)
PR: 272134
Differential Revision: https://reviews.freebsd.org/D39288

devel/py-pytest-cases: Add py-pytest-cases 3.6.14

Did you ever think that most of your test functions were actually the same test
code, but with different data inputs and expected results/exceptions?
- pytest-cases leverages pytest and its great @pytest.mark.parametrize
  decorator, so that you can separate your test cases from your test functions.
- In addition, pytest-cases provides several useful goodies to empower pytest.
  In particular it improves the fixture mechanism to support "fixture unions".
  This is a major change in the internal pytest engine, unlocking many
  possibilities such as using fixture references as parameter values in a test
  function. See here.

pytest-cases is fully compliant with pytest-harvest so you can easily monitor
the execution times and created artifacts. With it, it becomes very easy to
create a complete data science benchmark, for example comparing various models
on various datasets.