Hi all, I'm Mary, long time lurker. 
I searched the wiki, the meeting minutes, and messages, but I couldn't find an answer to my question. Sorry if it is a repeat. 

My problem is not with the ancient Python versions, or the stacked licenses listed for 2.0+. It's a matching guidelines issue for the Python-2.0 license text.
PSF lists its version numbers inside the license text, and the SPDX matching guidelines don't say specifically that I can ignore them, though I want to. There is also a slight change in wording (bold, below), and additional copyright years in clause 2, but not substantive differences. However, I follow the license list and the matching guidelines very strictly. 

SPDX License list Python-2.0 says: 

1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation.

More recent (since 2001, wow) PSF license statements include whichever version inside the license text found in source code files, most recent one for example:

1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 3.8.2 software in source or binary form and its associated documentation.

I downloaded the 3.8.2 release from python.org and this only seems to be true for one variant of the license text that is used in the PC version of Python:

https://github.com/python/cpython/blob/master/PC/store_info.txt#L101

and *not* in the main license file in the source code. It is also on the website: https://docs.python.org/3.9/license.html

I did find that there are a few variants out there that are possibly not covered:

https://github.com/python/cpython/blob/master/LICENSE

(years around line 75)

https://github.com/python/cpython/blob/master/Doc/license.rst

(different years again)

So basically they have three different license variants in their code base, sigh...

-- 
Armijn Hemel, MSc
Tjaldur Software Governance Solutions