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 <ro...@reportlab.com> 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. > > > $ 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 *.whl > Uploading distributions to https://upload.pypi.org/legacy/ > Uploading pyRXP-2.1.1-cp37-cp37m-manylinux1_i686.whl > 100%|████████████████████████████████████████████████████████████████████████████████████████████████████| > 104K/104K [00:00<00:00, > 141KB/s] > HTTPError: 400 Client Error: Invalid value for classifiers. Error: > 'License :: OSI Approved :: ReportLab BSD derived' is not a > valid choice for this field for url: https://upload.pypi.org/legacy/ This indicates that you're using a classifier which isn't actually registered. That causes the upload to be rejected. It is equivalent to trying to use a classifier that might claim support for Python 2.8 > > 1) I think it is completely wrong for twine/pypi to fail to upload because > of the license field. The license is derived from BSD > and the same string is present in the previously uploaded versions of this > package. What are valid licenses? Presumably pypi is > now a gatekeeper for the license police. > This seems harmfully rude and presumptive. I've explained the problem you're encountering above. Please assume the best going forward > > 2) I looked in vain on the new pypi.org site for a manual upload > mechanism. Is this now frowned on? > I'm not sure why a manual upload would be preferable here. > 3) I was able to upload the same package several times without error; does > this mean I am overwriting the file? > This seems unrelated and there's no information here to explain the question. Given that a file can not be deleted and re-uploaded to PyPI I'm guessing that you uploaded it once successfully and continue to run the same command. PyPI is ignoring those most likely or you're using twine's --skip-existing flag which allows uploads of more than one file to continue even if some are already uploaded -- > Robin Becker > -- > Distutils-SIG mailing list -- distutils-sig@python.org > To unsubscribe send an email to distutils-sig-le...@python.org > https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ > Message archived at > https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/RAFVT2Z23NZOAVURYKRASZTBWEGWSUDI/ >
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/HUPYQWS4M6VGBUR2WW2IOR57642XCVG3/
