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 license metadata field for traitlets contains the full license text instead of only the license specifier in the resulting METADATA file within the dist-info part of the traitlets package.
This then causes the field on pypi.org to also try to print the full license text.
I have no clue what causes this, though. The pyproject.toml in the repository looks just fine. I've seen other projects that have the same problem with similar config (specifying the license file in the license field and the short name in the classifiers - pipenv for example) , but I've also seen projects that do this without problems, so I'm at a loss as to what causes this.
Maybe it's got to do with some custom packaging script of yours that I couldn't find.
I hope one of the maintainers might immediately know what the problem is now that it's known. (I think you barely check the Metadata on the pypi page or your built packages after releasing an update)
The text was updated successfully, but these errors were encountered:
Hello,
the license metadata field for traitlets contains the full license text instead of only the license specifier in the resulting METADATA file within the dist-info part of the traitlets package.
This then causes the field on pypi.org to also try to print the full license text.
I have no clue what causes this, though. The pyproject.toml in the repository looks just fine. I've seen other projects that have the same problem with similar config (specifying the license file in the license field and the short name in the classifiers - pipenv for example) , but I've also seen projects that do this without problems, so I'm at a loss as to what causes this.
Maybe it's got to do with some custom packaging script of yours that I couldn't find.
I hope one of the maintainers might immediately know what the problem is now that it's known. (I think you barely check the Metadata on the pypi page or your built packages after releasing an update)
The text was updated successfully, but these errors were encountered: