[Distutils]Re: pypi/twine complains about license

2018-07-11 Thread Thomas Kluyver
On Wed, Jul 11, 2018, at 7:32 PM, Chris Jerdonek wrote: > And yet you can see "License: ReportLab BSD Derived" in the left-hand > column under "Meta," so how did it get there? Did PyPI previously fall > back to including the "License" classifier value as is (even if > invalid) if no "license"

[Distutils]Re: pypi/twine complains about license

2018-07-11 Thread Donald Stufft
> On Jul 11, 2018, at 12:37 PM, Nathaniel Smith wrote: > > Possibly PyPI is noticing that the file you're trying to upload is identical > to the one that's already there and counting that as a "successful upload"? Yes, if you try to upload the same file twice (same as in, the hashes match

[Distutils]Re: pypi/twine complains about license

2018-07-11 Thread Nathaniel Smith
PyPI is not the license police. You can specify any license you like in the dedicated, free-form text, "license" field. That's the "license" field. But, PyPI does require that values in the "classifiers" field have to be taken from a known set. Among other things, this prevents typos, and

[Distutils]Re: pypi/twine complains about license

2018-07-11 Thread Ian Stapleton Cordasco
Hi there Robin, I'm going to try to reply in-line. Sent from my phone with my typo-happy thumbs. On Wed, Jul 11, 2018, 11:17 Robin Becker wrote: > After release of Python-3.7 I wanted to upload to pypi a newly built > version of a C-extension which already has been migrated to > the new site.

[Distutils]Re: pypi/twine complains about license

2018-07-11 Thread Paul G
I think the issue here is not your use of the "license" field (though using the classifier-like syntax there is dubious), but the fact that you are specifying an invalid classifier. The valid classifiers are enumerated, you can find them here: https://pypi.org/classifiers/ I think the

[Distutils]pypi/twine complains about license

2018-07-11 Thread Robin Becker
After release of Python-3.7 I wanted to upload to pypi a newly built version of a C-extension which already has been migrated to the new site. $ twine --version twine version 1.11.0 (pkginfo: 1.4.2, requests: 2.18.1, setuptools: 36.2.0, requests-toolbelt: 0.8.0, tqdm: 4.14.0) $ twine upload