This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients docs@python, lemburg, poikilos
Date 2021-03-03.20:17:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614802640.89.0.923363464458.issue43391@roundup.psfhosted.org>
In-reply-to
Content
https://www.python.org/download/releases/2.4/license/ is the correct link for the Python 2.4 license.

Note that the contributor agreement allows the PSF to distribute the code under a different OSS license and so the current Python license applies for whatever version of Python you are using applies.

Peter Astrand still owns the copyright to the code he contributed and so the notice may not be removed until everything he contributed is gone. Even then, it's a courtesy to the author to leave an authorship notice in the code, since the original contribution motivated the API, which mostly still is in place. In fact, the contrib agreement probably doesn't even allow removing it at all, since it requires:

"""
Contributor shall identify each Contribution by placing the following notice in its source code adjacent to Contributor's valid copyright notice: "Licensed to PSF under a Contributor Agreement." 
"""

This is the original file which was added:

https://github.com/python/cpython/blob/5b3687df2e6dce2c09662ec9287e8f23075c4f1d/Lib/subprocess.py

At that time we did not have contributor agreements in place, AFAIR. The contrib agreement came later and allowed the removal of the verbatim 3-clause BSD license.

It's probably good idea to remove the reference to Python 2.4 from the doc-string.
History
Date User Action Args
2021-03-03 20:17:20lemburgsetrecipients: + lemburg, docs@python, poikilos
2021-03-03 20:17:20lemburgsetmessageid: <1614802640.89.0.923363464458.issue43391@roundup.psfhosted.org>
2021-03-03 20:17:20lemburglinkissue43391 messages
2021-03-03 20:17:19lemburgcreate