Distro Planets

PySCard 2.3.2 ships Python 3.14 and 3.15 binary wheels, drops SourceForge

Key Takeaway

PySCard 2.3.2 contains no code changes but adds pre-built binary wheels for Python 3.14 and 3.15 to PyPI, while completing the project's migration away from SourceForge distribution.

Summary

Ludovic Rousseau has published PySCard 2.3.2, a maintenance release of the Python PC/SC smart card library. The release contains no code changes; its sole purpose is to publish pre-compiled binary wheels for Python 3.14 and 3.15 on PyPI, targeting environments where rebuilding from source is impractical, particularly Windows systems. The release also finalizes the project's distribution migration by removing SourceForge as a download channel entirely, leaving PyPI as the exclusive source.

The PyPI source tarball currently triggers an "Incomplete provenance" warning because Rousseau manually uploaded it with twine. The next release is expected to use GitHub Actions for automated source uploads, matching the existing automated wheel publishing pipeline. This release follows the same manual twine process used historically.

Build system and distribution changes in PySCard 2.3.2

  • Python version support: Binary wheels are now available for Python 3.14 and 3.15, expanding platform coverage without requiring local compilation.
  • Distribution channel consolidation: SourceForge distribution has been removed entirely; PyPI is now the sole official source for PySCard releases.
  • Provenance gap: The source tarball pyscard-2.3.2.tar.gz carries an "Incomplete provenance" alert on PyPI due to manual twine upload rather than automated attestation.
  • CI/CD transition: Future releases will move source uploads to GitHub Actions, aligning with the existing automated wheel build and publish workflow.
  • Platform targeting: The wheel-focused release explicitly prioritizes Windows and other systems where rebuilding Python C extensions from source poses deployment friction.

Why it matters

For Linux distributions and system administrators, this release has minimal direct impact since PySCard is typically packaged through distro repositories rather than PyPI wheels. However, the completed SourceForge-to-PyPI migration and planned GitHub Actions automation for source artifacts improves supply-chain transparency for a foundational smart card library used in authentication, digital signature, and secure access workflows across the open-source security stack.

Original reference: blog.apdu.fr →