Re: pengines extension to html_requires

The real issue isn't options vs no options.  

As Jan says-

Note that a small interface has advantages in itself: documentation,
understanding and reducing the risk of forgetting arguments.

The real issue is that there's no clue which of these are rarely used by the end user,
or how the commonly used ones fit together. The documentation assumes knowledge of
concepts that aren't explained. The overview doesn't seem connected to actual use.

After struggling with this apparently more than any other outsider, I'm still stuck
with a single 'happy path' of slavishly imitating the examples, and not really understanding
how to go off and fly on my own.