Pulp

I suggest we use setuptools' extra_requires module [0]
Users can then install pulp like: pip install pulpcore['autodocs'] if they wish for pulpcore with autodocs, and pip install pulpcore if they do not

[0] http://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies

Yep!
pip install -e .['test'] for local installs
pip3 install -e "git+https://github.com/werwty/pulp.git@3.0-dev#egg=pulpcore[test]&subdirectory=plugin" for remote

In terms of a mechanism, I think having the optional setuptools approach is right.

I also want to hear feedback on this question: should all Pulp installations ship with local API docs by default?

I also want to hear feedback on this question: should all Pulp installations ship with local API docs by default?

Seems easier to just have a central place for users to see their api schema for their particular set up rather than having to hunt down the docs online for core, plugins, etc; and then have to look up what versions of things that are being used, etc.

Are there any downsides?

When I think of dependencies I think of things that pulp must have in order to run.

Tools like drf_openapi/drf_yawg is nice to have but not necessary; the schema is still available to the user when they GET /api/v3/; all this optional dependencies provide is a nice UI wrapper on top.

Superceded by: https://pulp.plan.io/issues/3552