On Sat, Jun 4, 2016 at 8:33 AM, Nathaniel Smith <njs@pobox.com> wrote:

How do you propose to implement and support this hypothetical doc service, given PyPI's resource constraints? Who's going to implement and maintain it? What other features are you suggesting be de-prioritized so that people can focus on this instead? Opportunity cost is a real cost.

Would it be worthwhile to write up a PEP specifying some kind of documentation API?

Having something well-specified would allow a motivated non-core-Warehouse dev to implement the details and (assuming it's as uncomplicated as I imagine) just create a PR. I assume it wouldn't really need much in the way of maintenance. But it would also give the RTD folks (and others?) the ability to implement their own tools for generating/hosting the docs.

-W