Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python 3.7.5 #9023

Merged
merged 3 commits into from
Apr 9, 2021
Merged

python 3.7.5 #9023

merged 3 commits into from
Apr 9, 2021

Conversation

clearlydefinedbot
Copy link
Contributor

Type: Missing

Summary:
python 3.7.5

Details:
Add PSF-2.0 License

Resolution:
License Url:
https://docs.python.org/3.7/license.html

Description:
Reading the license URL it seems to be the only choice which fits?

Pull request generated by Microsoft tooling.

Affected definitions:

@clearlydefinedbot
Copy link
Contributor Author

You can review the change introduced to the full definition at ClearlyDefined.

@TRQ3 TRQ3 self-assigned this Jan 8, 2021
@TRQ3
Copy link
Contributor

TRQ3 commented Jan 14, 2021

  1. Package files shows a rather long and unclear license file. Points to PSF 2.0. https://clearlydefined.io/file/1e28cb23e7511a272d5395e154e6540149a066e41903e72967c54df2582987ef
  2. Meta data links to same long and unclear license language as above. https://www.nuget.org/packages/python/3.7.5/License
  3. Nuspec does not show clear license, linking to a Microsoft site handling deprecated licenses.

Leaning toward PSF 2.0, but curious to hear if you agree @ariel11. There is a difference between Python 2.0 and PSF 2.0. The language in the license files mentioned above shows a differing license schedule for various versions, this specific package falling in the latest license indication.

@AE49
Copy link
Contributor

AE49 commented Jan 19, 2021

@capfei Declared license has been suggested as PSF-2.0. When I run the diff tool it seems the closest match is Python-2.0 but there are still some differences in the license text. How would you Declare this one?

@TRQ3

@capfei
Copy link
Member

capfei commented Jan 19, 2021

@AE49 I would curate as Python-2.0 since this is the Python license for Python 3.7.
https://docs.python.org/3.7/license.html

@ariel11 Thoughts?

@ariel11
Copy link
Contributor

ariel11 commented Jan 27, 2021

@TRQ3 - I am unclear on this one given the changes made to the license file. Let's discuss with broader community. Thanks

@ariel11 ariel11 assigned ariel11 and unassigned TRQ3 Feb 23, 2021
@github-actions github-actions bot added the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Feb 23, 2021
@ariel11 ariel11 mentioned this pull request Mar 5, 2021
@ariel11
Copy link
Contributor

ariel11 commented Mar 18, 2021

Checking with SPDX: spdx/license-list-XML#1200

@ariel11
Copy link
Contributor

ariel11 commented Apr 8, 2021

@capfei / @royaljust - The below shows a portion of a comparison between the actual Python project license file and the SPDX "Python-2.0." Given the differences, I think our guidelines (and the SPDX matching guidelines) would indicate we should curate this as "OTHER." Do you agree? If a SPDX identifier is later created for the actual Python project license, we could submit a PR to update these.

image

@github-actions
Copy link

github-actions bot commented Apr 9, 2021

Conflicts have been resolved.

@github-actions github-actions bot removed the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Apr 9, 2021
@ariel11 ariel11 merged commit 793bece into master Apr 9, 2021
@ariel11 ariel11 deleted the clearlydefinedbot_210108_205733.005 branch April 9, 2021 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants