Build memray from main for the py315 env

memray 1.19.3 predates the 3.15 support merged in bloomberg/memray#920 and
ships no cp315 wheels, so pip falls back to the sdist and the C extension
build fails on the runner. Until a memray release covers 3.15, the py315
tox env installs memray from git main and the py315 CI leg alone gains the
apt packages memray's own CI uses to build it. All other legs keep
installing released memray from PyPI; the pin and the extra CI step should
both be dropped once cp315 wheels are published.

Signed-off-by: Bernát Gábor <gaborjbernat@gmail.com>

Author: gaborbernat

.github/workflows/build.yml

@@ -42,6 +42,10 @@ jobs:
         uses: actions/setup-python@v6.3.0
         with:
           python-version: ${{ matrix.py }}-dev
+      # memray has no cp315 wheels yet, so py315 builds it from source
+      - name: install memray build dependencies
+        if: matrix.tox_env == 'py315'
+        run: sudo apt-get update -q && sudo apt-get install -qy libdebuginfod-dev libunwind-dev liblz4-dev pkg-config
       - name: setup test suite ${{ matrix.tox_env }}
         run: tox -vv --notest -e ${{ matrix.tox_env }}
       - name: run test suite ${{ matrix.tox_env }}

tox.ini

@@ -34,6 +34,11 @@ allowlist_externals =
 package = wheel
 wheel_build_env = .pkg
 
+[testenv:py315]
+deps =
+    # memray 1.19.3 ships no cp315 wheels; use main until a release with 3.15 support
+    memray @ git+https://github.com/bloomberg/memray.git
+
 [testenv:py312-cov]
 commands =
     make coverage