head 1.2; access; symbols pkgsrc-2026Q2:1.2.0.8 pkgsrc-2026Q2-base:1.2 pkgsrc-2026Q1:1.2.0.6 pkgsrc-2026Q1-base:1.2 pkgsrc-2025Q4:1.2.0.4 pkgsrc-2025Q4-base:1.2 pkgsrc-2025Q3:1.2.0.2 pkgsrc-2025Q3-base:1.2 pkgsrc-2025Q2:1.1.0.2 pkgsrc-2025Q2-base:1.1; locks; strict; comment @# @; 1.2 date 2025.08.22.07.14.14; author adam; state Exp; branches; next 1.1; commitid TRcjcRyF4sFbbH7G; 1.1 date 2025.04.22.11.26.52; author adam; state Exp; branches; next ; commitid 3mzSQpoQlxKYu2SF; desc @@ 1.2 log @py-test-run-parallel: updated to 0.6.1 0.6.1 Fix thread-unsafe detection for indented tests Run coverage externally to load before plugins @ text @@@comment $NetBSD: PLIST,v 1.1 2025/04/22 11:26:52 adam Exp $ ${PYSITELIB}/${WHEEL_INFODIR}/METADATA ${PYSITELIB}/${WHEEL_INFODIR}/RECORD ${PYSITELIB}/${WHEEL_INFODIR}/WHEEL ${PYSITELIB}/${WHEEL_INFODIR}/entry_points.txt ${PYSITELIB}/${WHEEL_INFODIR}/licenses/LICENSE ${PYSITELIB}/${WHEEL_INFODIR}/top_level.txt ${PYSITELIB}/pytest_run_parallel/__init__.py ${PYSITELIB}/pytest_run_parallel/__init__.pyc ${PYSITELIB}/pytest_run_parallel/__init__.pyo ${PYSITELIB}/pytest_run_parallel/cpu_detection.py ${PYSITELIB}/pytest_run_parallel/cpu_detection.pyc ${PYSITELIB}/pytest_run_parallel/cpu_detection.pyo ${PYSITELIB}/pytest_run_parallel/plugin.py ${PYSITELIB}/pytest_run_parallel/plugin.pyc ${PYSITELIB}/pytest_run_parallel/plugin.pyo ${PYSITELIB}/pytest_run_parallel/thread_comparator.py ${PYSITELIB}/pytest_run_parallel/thread_comparator.pyc ${PYSITELIB}/pytest_run_parallel/thread_comparator.pyo ${PYSITELIB}/pytest_run_parallel/thread_unsafe_detection.py ${PYSITELIB}/pytest_run_parallel/thread_unsafe_detection.pyc ${PYSITELIB}/pytest_run_parallel/thread_unsafe_detection.pyo ${PYSITELIB}/pytest_run_parallel/utils.py ${PYSITELIB}/pytest_run_parallel/utils.pyc ${PYSITELIB}/pytest_run_parallel/utils.pyo @ 1.1 log @py-test-run-parallel: added version 0.4.0 This pytest plugin takes a set of tests that would be normally be run serially and execute them in parallel. The main goal of pytest-run-parallel is to discover thread-safety issues that could exist when using C libraries, this is of vital importance after PEP703, which provides a path for a CPython implementation without depending on the Global Interpreter Lock (GIL), thus allowing for proper parallelism in programs that make use of the CPython interpreter. @ text @d1 1 a1 1 @@comment $NetBSD$ d11 3 d17 6 @