kernc

This looks like one of the [mock bugs in Python](https://bugs.python.org/issue?%40columns=id%2Cactivity%2Ctitle%2Ccreator%2Cassignee%2Cstatus%2Ctype&%40sort=-activity&%40filter=status&%40action=searchid&ignore=file%3Acontent&%40search_text=mock+inspect&submit=search&status=-1%2C1%2C3) since `inspect.signature(MockService.run)` is what raises. I guess we can apply the proposed workaround. Can you make it a pull request?

> ```diff > + return inspect.isroutine(obj) and callable(obj) and not isinstance(obj, Mock) > ``` This will then fall through to interpreting `MockService.run` as a non-callable _variable_. How do we feel...

> Just want to throw the question though, how will moving the supported base version of Python from 3.5+ to 3.6+ impact `pdoc`'s users? Updating all docs to use f-strings...

> Should there be a code style section added to CONTRIBUTING.md to specify formatting preference to keep things neat moving ahead? Rather still I'd have it covered in CI like...

Unless the function is some class' `__init__` constructor and the variables are attributes set upon `self` (effectively becoming [documented _instance variables_](https://pdoc3.github.io/pdoc/doc/pdoc/#docstrings-for-variables)), this doesn't nor is it customary to work. Function-local...

Seems like compatibility with Sphinx and PyDoctor is [a feature of doc2dash itself](https://doc2dash.readthedocs.io/en/stable/formats.html)? Not sure what to do about it here. :grimacing: Have you tried creating Dash docsets [from any...

The issue is we already skip `mwe.module` when iterating over submodules: https://github.com/pdoc3/pdoc/blob/1de51a9d7c2f80412d877066f62c57d4100226c7/pdoc/__init__.py#L655-L656 I guess the warning might try to account for that ...

> (i.e. a warning is generated) when the module is a sub-sub-module. Can you show a mwe? > where objects/modules can simply set `__pdoc__ = False` Simply setting: ```py __pdoc__...

We do. :smile: Integrated, but optional behind a [config toggle](https://pdoc3.github.io/pdoc/doc/pdoc/#custom-templates), would indeed make sense. Or even something purely JS-based that shows a light switch on the client side for the...

Or, if the way of a config tunable, a dict of preferred style colors would empower the user more. Something like: ```py # config.mako: bright_color_theme = dict(foreground='black', background='white', link='...', ...)...