CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

devel/py-pytest-cpp 2.6.0

Use pytest runner to discover and execute C++ tests

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 2.6.0
Upstream
up to date
Last update
to 2.6.0 · 659343d7d6
Quarterly
2026Q4: 2.6.0
WWW
https://github.com/pytest-dev/pytest-cpp
Links
cgit · VuXML

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 2.6.0.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (7)

Po-Chuan Hsieh (sunpoet) · 2.6.0
devel/py-pytest-cpp: Update to 2.6.0

Changes:	https://github.com/pytest-dev/pytest-cpp/releases
		https://github.com/pytest-dev/pytest-cpp/blob/master/CHANGELOG.md
659343d7d6
Po-Chuan Hsieh (sunpoet) · 2.5.0_1
devel/py-pytest-cpp: Convert to USE_PYTHON=pep517

- Bump PORTREVISION for package change
f4c0e3d9e3
Charlie Li (vishwin) · 2.5.0
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
5d4139f8bd
Po-Chuan Hsieh (sunpoet) · 2.5.0
devel/py-pytest-cpp: Update to 2.5.0

- Add GitHub to MASTER_SITES

Changes:	https://github.com/pytest-dev/pytest-cpp/releases
		https://github.com/pytest-dev/pytest-cpp/blob/master/CHANGELOG.md
e897726f90
Po-Chuan Hsieh (sunpoet) · 2.4.0
devel/py-pytest-cpp: Update to 2.4.0

Changes:	https://github.com/pytest-dev/pytest-cpp/releases
		https://github.com/pytest-dev/pytest-cpp/blob/master/CHANGELOG.md
57c557986f
Rene Ladan (rene) · 2.3.0
all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>
3d9a815d9c
Po-Chuan Hsieh (sunpoet) · 2.3.0
devel/py-pytest-cpp: Add py-pytest-cpp 2.3.0

pytest-cpp uses pytest runner to discover and execute C++ tests. It supports
Google Test, Boost.Test, and Catch2.

This brings several benefits:
- Allows you to run all your tests in multi-language projects with a single
  command;
- Execute C++ tests in parallel using pytest-xdist plugin;
- Use --junitxml option to produce a single and uniform xml file with all your
  test suite results;
- Filter which tests to run using standard test filtering capabilities, such as
  by file names, directories, keywords by using the -k option, etc.;
daf74492d8