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

License metadata seems to be ignored #3225

Closed
pganssle opened this issue Mar 11, 2018 · 4 comments
Closed

License metadata seems to be ignored #3225

pganssle opened this issue Mar 11, 2018 · 4 comments
Labels
feature request needs discussion a product management/policy issue maintainers and users should discuss requires triaging maintainers need to do initial inspection of issue

Comments

@pganssle
Copy link
Contributor

When I made the latest release of python-dateutil, it came along with a license change from BSD to Apache / BSD dual licensed. I updated the license= metadata in setup.py, but I forgot to update the trove classifiers.

The page on PyPI shows the license as "Apache 2.0" as I would expect. The page on warehouse shows the license as "BSD License". I'm assuming it's pulling that from the trove classifier? Shouldn't it pull it from the license field if that is populated?

@brainwane brainwane added requires triaging maintainers need to do initial inspection of issue feature request needs discussion a product management/policy issue maintainers and users should discuss labels Mar 12, 2018
@di di closed this as completed in #3236 Mar 12, 2018
@di
Copy link
Member

di commented Mar 12, 2018

Thanks for raising @pganssle, this was indeed a small bug with the way we were handling the presence of licenses in both the Classifier field and the License field.

Based on the specification above, I would suggest the following setup.py for future releases:

setup(
    ...
    classifiers=[
        ....
        'License :: OSI Approved :: BSD License',
        'License :: OSI Approved :: Apache Software License',
        ....
    ],
    license = 'Dual License'
    ...
)

Which will show up on pypi.org as:

License: BSD License, Apache Software License (Dual License)

Also, in #pypa on IRC you said:

Did I screw this up? https://test.pypi.org/project/python-dateutil/
I'm listed as Author.
But setup.py has me as maintainer: https://github.com/dateutil/dateutil/blob/master/setup.py#L33

But looking at the metadata for the 2.7.0 source distribution, all I'm seeing is:

Author: Paul Ganssle
Author-email: [email protected]

which leads me to think that this was changed after you made the distribution file, but let me know if you're still having issues with it.

@dstufft
Copy link
Member

dstufft commented Mar 13, 2018 via email

@pganssle
Copy link
Contributor Author

@di Thanks for the response. I updated the trove classifiers, I think your idea of changing license= to Dual License is a good idea, I'll do that shortly.

With regards to the maintainer/author thing, I've opened an issue about it: pypa/setuptools#1288, I'm also going to open one for distutils.

@di
Copy link
Member

di commented Mar 13, 2018

Yeah, that seems like a bug. Warehouse will correctly handle the presence of any or all of the Author/Maintainer metadata fields, if they're correctly provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request needs discussion a product management/policy issue maintainers and users should discuss requires triaging maintainers need to do initial inspection of issue
Projects
None yet
Development

No branches or pull requests

4 participants