[AstroPy] descriptive package descriptions?
mcraig at mnstate.edu
Sun Nov 20 20:29:21 EST 2016
I believe the one line descriptions are generated from the description argument in setup.py, though it is possible to override that manually. Not sure why some have “No summary.”
I can update the “No summary” ones over thanksgiving (I’m one of the maintainers of the conda channel) and am happy to update any other summaries package owners want to change….when the build mechanism is working well I never see the summaries and would be reluctant to edit on the fly in any event.
Department of Physics and Astronomy
Minnesota State University Moorhead
1104 7th Ave S, Moorhead MN 56563
office: Hagen 307F
phone: (218) 477-2439
fax: (218) 477-2290
On Nov 20, 2016, at 3:10 PM, Peter Teuben <teuben at astro.umd.edu<mailto:teuben at astro.umd.edu>> wrote:
the one line packages descriptions, as for example seen on anaconda's
could use some cleanup/normalization. How are these generated? The astropy group could make them more coherent between them. I'm thinking of the unix man page description under the NAME field. A few are still labeled "No Summary", and my eye also caught an author's colorful opinion.
The entry for "emcee" is labeled "kick ass blablabla". Perhaps cute in 2015. But I really object to putting an opinion in a searchable line like that. We should stick to facts. I'm not even sure how to measure kick-ass anyways. And how is one to trump that one, if one ever write one that actually runs in reasonable time There will be no end in sight in the language we'll have to use to describe codes.
AstroPy mailing list
AstroPy at scipy.org<mailto:AstroPy at scipy.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the AstroPy