On Tue, Jul 15, 2014 at 2:24 AM, Wichert Akkerman <wich...@wiggy.net> wrote: > >> On 15 Jul 2014, at 11:22, Richard Jones <rich...@python.org> wrote: >> >> Hi, I just want to note that I'm aware of this issue and I have "do >> something about it" in my long TODO. >> >> That link is malformed in any case - docutils just passes it on through and >> you're just lucky that browsers will guess that it is supposed to have a >> "http://"; scheme on the front. PyPI does indeed check URL schemes in links >> for security reasons. I guess I never though that I'd need to allow a blank >> one - I'd have to think about the implications of allowing it. > > I don’t particularly mind PyPI refusing URL without a scheme – that is a > perfectly reasonably precaution. The problem is that there is no way at all > to see why PyPI was refusing to render my ReST without manually bisecting the > long description manually through its web-interface.
One possible interim solution is to add a "check ReST" form to PyPI's web UI. The form could simply display the error output of running PyPI's conversion to HTML on whatever text is given. That would address Donald's point that it's not acceptable to fail an upload, while still giving people *some* reasonable way to troubleshoot failures. The existence of the validation form could be documented in the PyPI upload docs. --Chris _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
