…adata

Fixes #86

Removed cffi package version 1.17.1 and its dependencies from the lock file.

Co-Authored-By: Claude <noreply@anthropic.com>

Co-Authored-By: Claude <noreply@anthropic.com>

Assign callgrind_start_instrumentation and callgrind_stop_instrumentation
as instance attributes pointing straight at the native C functions
instead of routing through Python wrapper methods. This removes one
Python stack frame from the hot path around instrumented code, which
matters because Valgrind/callgrind measurements include every frame
that's live while instrumentation is on.

Co-Authored-By: Claude <noreply@anthropic.com>

Declare the dist_instrument_hooks module as supporting the free-threaded
build by calling PyUnstable_Module_SetGIL(Py_MOD_GIL_NOT_USED) under
Py_GIL_DISABLED. Without this, importing the extension on a free-threaded
interpreter re-enables the GIL and emits a RuntimeWarning. The underlying
instrument-hooks C library uses its own internal locking, so the module
is safe to run without the GIL.

Co-authored-by: Claude <noreply@anthropic.com>

Transpiled code generates these.

* build: enable free-threaded wheels in cibuildwheel

cibuildwheel does not build free-threaded CPython wheels by default, even
when the build pattern matches cp*. As a result, users on 3.13t/3.14t/3.15t
installed pure-Python wheels with no native extension and saw:

    Failed to load instrument hooks library: cannot import name
    'dist_instrument_hooks' from 'pytest_codspeed.instruments.hooks'

Opt in via `enable = ["cpython-freethreading"]` so the cp31{3,4,5}t wheels
ship the compiled dist_instrument_hooks extension.

Co-Authored-By: Claude <noreply@anthropic.com>

* ci: bump pypa/cibuildwheel from v3.2.1 to v3.4.1

v3.2.1 predates CPython 3.14/3.15 support in cibuildwheel. Bumping unlocks
free-threaded 3.14t/3.15t wheel builds (which no longer need the
cpython-freethreading enable flag — only 3.13t does).

Co-Authored-By: Claude <noreply@anthropic.com>

* build: enable cpython-prerelease wheels in cibuildwheel

CPython 3.15 is still in beta, so cibuildwheel will not build cp315 /
cp315t wheels without the cpython-prerelease opt-in. Add it alongside
cpython-freethreading so prerelease wheels (regular + free-threaded)
ship for users testing on 3.15.

Co-Authored-By: Claude <noreply@anthropic.com>

* chore: advertise Python 3.15 support in classifiers

Add the trove classifier for 3.15 now that cibuildwheel ships cp315 /
cp315t wheels.

Co-Authored-By: Claude <noreply@anthropic.com>

* ci: pin cibuildwheel to a main commit with CPython 3.15 support

v3.4.1 does not yet include cp315 in its bundled build-platforms.toml, so
the cpython-prerelease enable flag has nothing to act on. Pin to commit
ec0977e (post-#2833 "add CPython 3.15 beta 1") to unblock cp315 / cp315t
wheel builds. Drop the pin back to a tagged release once cibuildwheel
ships 3.15 metadata.

Co-Authored-By: Claude <noreply@anthropic.com>

* build: drop cpython-freethreading enable group

The cibuildwheel commit we pin (post-#2684) no longer recognizes
cpython-freethreading: 3.13t support was dropped and free-threading is the
default for 3.14+. Keeping the value triggers:

    cibuildwheel: Failed to parse enable group. Unknown enable group:
    cpython-freethreading.

Only cpython-prerelease is still needed (for cp315 / cp315t while 3.15 is
in beta).

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

Adds a callgrind_add_obj_skip C extension function that emits the
Valgrind client request VG_USERREQ__ADD_OBJ_SKIP (0x43540006), and a
callgrind_skip_python_runtime() helper that skips libpython and the
python executable. Called from InstrumentHooks.__init__ so Python runtime
frames stop polluting the callgrind flamegraph (COD-2654).

Drop the locally-defined VG_USERREQ__ADD_OBJ_SKIP trapdoor and the
Python-side realpath resolution. Both now live in instrument-hooks
(65a7afb), so the binding just forwards to the shared helper.

Refs COD-2658.