Collaborative Working Sessions - Python

attestation for python

short recap on trusted publishing:

general discussion

python-sphinx may include sixstore and might give an example how to do attestation. getting source code versions out of pypi is very hard/difficult or not even possible for many packages

ossrebuild has a project which tries to find the right source code of a pypi package. ossrebuild provide attestation for rebuilds.

In the whl archive is a WHEEL file, which describes some environment/meta data.

How to specify the build environment? How to sepcify the run time environment?

E.g. compiling lxml python module or psql, they require toolchains.

What does in-toto specify about dependencies?

.buildinfo is required, either as part of the attestation or as artifact.

attestation might have useful information to rebuild, but was created for a different reason

github runners are fully packed and changes over time. the github workflow will run on different runners over time.

The package manager could do a lot of things to help r-b.

pushing through the pep takes a long time. maybe try to do an experimental approach to add support for a package manager (e.g. hatch or other).