On 10/15/2015 12:18 AM, Robert Collins wrote:
On 15 October 2015 at 11:11, Thomas Goirand <z...@debian.org> wrote:
One major pain point is unfortunately something ridiculously easy to
fix, but which nobody seems to care about: the long & short descriptions
format. These are usually buried into the setup.py black magic, which by
the way I feel is very unsafe (does PyPi actually execute "python
setup.py" to find out about description texts? I hope they are running
this in a sandbox...).
Since everyone uses the fact that PyPi accepts RST format for the long
description, there's nothing that can really easily fit the
debian/control. Probably a rst2txt tool would help, but still, the long
description would still be polluted with things like changelog, examples
and such (damned, why people think it's the correct place to put that...).
The only way I'd see to fix this situation, would be a PEP. This will
probably take a decade to have everyone switching to a new correct way
to write a long & short description...
Perhaps Debian (1 thing) should change, rather than trying to change
all the upstreams packaged in it (>20K) :)
+1. Both README and PyPI are for users, and I personally find detailed
descriptions (especially a couple of simple examples) on the PyPI page
to be of so much value.
-Rob
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
