https://www.python.org/downloads/release/python-358/ has a .xz and a .tgz. At this moment, the .xz tarball is actually 3.5.8-rc2 rebranded as 3.5.8. This means it is missing the fix for bpo-38243 mentioned at https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-8-final
I have emailed email@example.com, suggesting a reroll as 3.5.9 to remove any confusion.
Thank you for the heads-up and report Peter
If you could keep us abreast of updates from firstname.lastname@example.org if they are forthcoming and no public upstream issue is created for this, that would greatly appreciated
the .xz link now has the correct MD5 and the correct contents.
(I have had no word from upstream.)
Thanks for the heads-up. During the 3.5.8 release process, I actually generated the tarball multiple times, and although I never officially released these previous versions, somehow the CDN latched onto this one .xz file from one of these test versions. As you note, the MD5 sum and file size on the release page were correct for the final version; also, the v3.5.8 tag in the Git repo and the GPG checksum file also match this final (correct) version.
Still, it's a messy situation. Fedora has already updated to 3.5.8, and they got the tarball without the fix for bpo-38243.
As you suggest, the best way to ameliorate this debacle is to just release a 3.5.9. I'll do that in the next day or so. In the meantime I'll send a quick note to the clp newsgroups.
Sorry - previous comment is the response from email@example.com.
Date: Sat Nov 2 06:25:16 2019
New Revision: 516287
- Update python35 to 3.5.9