kernc
kernc
> A simple workaround is to use a modified template and set the max length to `float('inf')` or something big like 9999999 to avoid shortening the description Another workaround might...
Might you export the notebook to Markdown and use [`.. include::` reStructuredText directive](https://pdoc3.github.io/pdoc/doc/pdoc/#supported-rest-directives)?
How exactly would the proposed feature be used? I admit I don't envision it clearly. What would the "different TOC" be? Would every module's TOC link to the extra pages...
> This would be super useful for machine learning related projects! In [another project](https://kernc.github.io/backtesting.py/doc/backtesting/#tutorials) I use a pipeline with [`nbconvert`](https://github.com/jupyter/nbconvert) to translate IPython notebooks and link them manually. I agree...
Listing absolute [refnames](https://pdoc3.github.io/pdoc/doc/pdoc/#pdoc.Doc.refname) only in the top-level module should work. This maybe alleviates part of your issue? ```py # project/__init__.py: try: from _private_build import __pdoc__ except ImportError: pass # Public...
Yeah, I guess the exceptions are explicit. `__pdoc__` can be constructed in Python code, though. Something like this should work: ```py # _private_build.py ... import _private_module _private_module.__pdoc__ = {refname: True...
If you look at it closely, it's inserted as `sex : (, )` into HTML, resulting in some invalid HTML. But I don't think it's a bug necessarily, because the...
Thanks for these issues! > * the variable `MY_VAR` is not documented at all `MY_VAR` is neither function nor class and it doesn't have a PEP 224 variable docstring, so...
It is. But that's in the module `_internal`, I suppose, not in the module where `__all__` is defined and `MY_VAR` exported ...
> Is there a conceptual reason why variables are handled differently? Yeah, there's no way to access PEP224 docstrings at runtime (i.e. via `__doc__`), so we parse source code ASTs...