[issue40293] cpython-source-deps project missing release for libffi commits

Gregory Szorc added the comment: I don't like utilizing the dynamic archive links like https://github.com/python/cpython-source-deps/archive/libffi.zip (even if you pin the commit) because GitHub does not guarantee the file content is deterministic over time. I perform SHA-256 validation of

[issue40293] cpython-source-deps project missing release for libffi commits

Steve Dower added the comment: To save the clicks, here's the URL that will get the latest sources from the libffi branch: https://github.com/python/cpython-source-deps/archive/libffi.zip -- ___ Python tracker

[issue40293] cpython-source-deps project missing release for libffi commits

Steve Dower added the comment: In master, we build against the latest build out of that repo, which comes from the libffi branch (not the 3.3.0 RC). In 3.8 (and 3.7? I forget) we use the 3.3.0 RC build. There's no later release from libffi (last I checked), and no important fixes since then

[issue40293] cpython-source-deps project missing release for libffi commits

New submission from Gregory Szorc : The https://github.com/python/cpython-source-deps project is missing a source archive release for commits to libffi needed to support building on Windows. The latest release of libffi is version libffi-3.3.0-rc0-r1, which corresponds to https://github.com/