I know you're probably tired of talking about the Python license, but...


mhardy@...
 

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.

The matching guidelines say: Text that can be considered omitable for matching purposes is indicated in the SPDX License List template with mark-up and in the corresponding HTML pages with colored text.

Is this the kind of variation that fits within the matching guidelines? Or, do we simply need to update the SPDX entry for Python-2.0 with colored text so it can flex on these minor changes across the modern versions? The old licenses in the stack aren't going to change, so it seems like an easy fix.

This isn't just a version 3 thing, I have seen this on v2.4 files recently.

If this has already been planned for the next license list update, I apologize. I may have missed it in the meeting minutes.

Thank you! Mary

Join Spdx-legal@lists.spdx.org to automatically receive all group messages.