You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: