> On 20 Oct 2017, at 17:51, Wes Turner <wes.tur...@gmail.com> wrote: > > > > On Friday, October 20, 2017, Ronald Oussoren <ronaldousso...@mac.com > <mailto:ronaldousso...@mac.com>> wrote: > >> On 28 Aug 2017, at 00:12, Brett Cannon <br...@python.org >> <javascript:_e(%7B%7D,'cvml','br...@python.org');>> wrote: >> >> If you search the archive of this mailing list you will notice I asked this >> exact question about a month or 2 ago (I think). The answer I got was it is >> used on PyPI.org <http://pypi.org/>, but I don't know how to set it with >> setuptools (flit will probably add support after PEP 517). > > To get back to this: I’m probably doing something wrong, but I haven’t > managed yet to make anything show up on PyPI.org <http://pypi.org/> when I > use “Project-URL” in metadata. > > There’s a pyobjc-core 4.0.1b1 wheel on PyPI.org <http://pypi.org/> that > includes two Project-URL lines in its metadata, but that doesn’t add anything > to the sidebar. I’ve manually verified that the metadata is present in the > wheel file (as I’m using a replacement egg_info command in my setup.py file > to generate this part of the metadata). > > https://github.com/pypa/warehouse/search?utf8=✓&q= > <https://github.com/pypa/warehouse/search?utf8=%E2%9C%93&q=>"project-url"&type=Issues > > https://github.com/pypa/warehouse/search?q= > <https://github.com/pypa/warehouse/search?q=>"Project-Url"&type=Commits&utf8=✓
I’m note sure what you’re trying to say here, but <https://github.com/pypa/warehouse/pull/878/files <https://github.com/pypa/warehouse/pull/878/files>> suggests that Project-URL is supported in the PyPI.org <http://pypi.org/> UI (assuming that it is running a version of the software from after merging this pull request). But for some reason this doesn’t work for me, and I don’t know why. Either I’m doing something wrong, or the code receiving wheel files does not yet store project-urls information in the database. > > > Ronald > > P.S. I tried to upload to test.pypi.org <http://test.pypi.org/>, but that > didn’t work due to an SSL error: > > $ twine upload -r testpypi > dist/pyobjc_core-4.0.1b1-cp27-cp27m-macosx_10_6_intel.whl > Uploading distributions to https://test.pypi.org/legacy/ > <https://test.pypi.org/legacy/> > Uploading pyobjc_core-4.0.1b1-cp27-cp27m-macosx_10_6_intel.whl > SSLError: HTTPSConnectionPool(host='test.pypi.org <http://test.pypi.org/>', > port=443): Max retries exceeded with url: /legacy/ (Caused by > SSLError(SSLError(1, u'[SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert > protocol version (_ssl.c:661)'),)) > > https://www.google.com/search?q=TLSV1_ALERT_PROTOCOL_VERSION > <https://www.google.com/search?q=TLSV1_ALERT_PROTOCOL_VERSION> > > Looks like TLSv1 (TLS 1.0) is deprecated. > > https://www.google.com/search?q=TLSV1_ALERT_PROTOCOL_VERSION+twine > <https://www.google.com/search?q=TLSV1_ALERT_PROTOCOL_VERSION+twine> > > https://github.com/pypa/twine/issues/273 > <https://github.com/pypa/twine/issues/273> Hmm… that issue means I should be slightly worried, the VM I’m using for uploading releases might stop working for this some time in the future. Hopefully upgrading the python installation on that will avoid that. Ronald
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
