Skip to content

License changed to Other/Proprietary #138

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

Closed
aroelo opened this issue Jan 18, 2022 · 1 comment · Fixed by #139
Closed

License changed to Other/Proprietary #138

aroelo opened this issue Jan 18, 2022 · 1 comment · Fixed by #139

Comments

@aroelo
Copy link

aroelo commented Jan 18, 2022

The latest release (0.3.2) has a license classified as 'Other/Proprietary License' on PyPI.
It does show some info regarding the Apache License, Version 2.0, but this is in the 'Meta' part and between brackets.

This changed license classification might cause issues for some users, for example the license checking tool that we use to check our dependencies (https://github.com/dhatim/python-license-check) classifies this now as using a 'Other/Proprietary License' instead of the expected Apache-2.0

@ghost
Copy link

ghost commented Jan 18, 2022

We have the same problem. This appeared with the switch to Poetry. Poetry only parses licences that contain a precise licence registry identifier (see pilosus/pip-license-checker#81) and the licence tag here is not like that. Therefore the licence tag in the build's metadata is still set correctly, but the corresponding classifier is not.

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 a pull request may close this issue.

1 participant