[issue37967] release candidate is not gpg signed (and missing release workflow)?

László Kiss Kollár added the comment: We are seeing the same issue with 3.8b4: + curl -fsSLO https://www.python.org/ftp/python/3.8.0/Python-3.8.0b4.tgz + curl -fsSLO https://www.python.org/ftp/python/3.8.0/Python-3.8.0b4.tgz.asc + gpg --verify Python-3.8.0b4.tgz.asc gpg: Signature made Thu 29

[issue37967] release candidate is not gpg signed (and missing release workflow)?

Ned Deily added the comment: The description of this issue is incorrect. All the release artifacts for the 3.8.0b3 have GPG signatures available - see https://www.python.org/downloads/release/python-380b3/ - like all other releases. Looking at the log of the failed Travis run in

[issue37967] release candidate is not gpg signed (and missing release workflow)?

Change by Karthikeyan Singaravelan : -- nosy: +lukasz.langa, ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37967] release candidate is not gpg signed (and missing release workflow)?

New submission from mattip : Over at [multibuild](https://github.com/pypa/manylinux/pull/333#issuecomment-519802858), they ran into an issue trying to build c-extensions with the 3.8rc3 since it seems it is not gpg signed. I could not find a HOWTO_RELEASE document to check that the release