Publish current libpff-python wheels to PyPI, including CPython 3.14

[adrianweidig]

Request

Could you publish a new libpff-python release to PyPI so that the wheels already produced by the current build workflow, including CPython 3.14 wheels, become installable with pip?

Current state

• PyPI currently offers only libpff-python 20231205; its latest Windows/Python combination does not include CPython 3.14.
• Current main is commit e9b304c79a8dcdff7b11529022b2dfd8bf64a20f.
• The official build_wheels run 28315910150 completed successfully on 2026-06-28.
• Its official cibw-wheels-windows-latest-1 artifact contains:
  • libpff_python-20260625-cp314-cp314-win_amd64.whl
  • libpff_python-20260625-cp314-cp314-win32.whl
  • free-threaded cp314t variants as well as wheels for older CPython versions.
• GitHub reports SHA-256 2b708a88271725c89b813833ce7ddc0e95ebfb5c54e8604253614e6c1dc75a3d for that complete Windows artifact.

Independent Windows x64 verification

I downloaded the artifact through the GitHub API, verified the artifact digest above, and tested the regular x64 wheel in a clean CPython 3.14.6 virtual environment on Windows 11:

Python: 3.14.6, win-amd64
Wheel: libpff_python-20260625-cp314-cp314-win_amd64.whl
Wheel SHA-256: d59cc186f4255bf832a6310ab533e0b5dbf235098fcce53daae4f99d8f6b39de
pip check: No broken requirements found.
import pypff: successful
pypff.get_version(): 20260625
Extension: pypff.cp314-win_amd64.pyd
python tests/runtests.py: OK (57 tests, 53 skipped because no PST test input was present)

The official cibuildwheel job also completed its configured python tests/runtests.py test command successfully.

Suggested maintainer action

The existing .github/workflows/build_wheel.yml already builds the sdist and platform wheels and has TestPyPI/PyPI publication jobs gated on release.published. Therefore I do not see a source-code or workflow change that needs a pull request.

Would you be willing to publish a new GitHub release/tag (for example the current generated version 20260625, if that matches your release policy) and let the existing trusted-publishing jobs upload the artifacts to PyPI?

This would make direct PST access available to regular CPython 3.14 users on Windows without requiring a local Visual Studio build.

[joachimmetz]

Per #2 Python bindings are not ready.

If you want to test with a wheel you can find build artifacts attached to the run (e.g. https://github.com/libyal/libpff/actions/runs/30003155990)

I take a look at pushing a new release, when time and priorities permits.