Wessel

Hey @francesco-ballarin! Thanks for opening this issue. Oof, whereas `help(f)` now is much more helpful, it totally slipped my mind that whatever `f.__doc__` returns should also be nicely rendered by...

Great! And yes, you’re totally right about the test case. I might not have time to work on this in the next week and a half, but after that I...

Just a brief update! A function with the following docstring ```python def test(x): """Test. Args: x (int): `x`. Returns: int: Sum. This function has further implementations documented below. .. py:function::...

Perfect, @francesco-ballarin! I'll release a new version this weekend that includes this change.

Sorry for not having released a new version yet. I'm working on it. I came across a few subtle bugs in the process resolving which is taking a while.

This has been incorporated in the latest release `v2.1.0`. An example in the Plum documentation can be found [here](https://beartype.github.io/plum/api.html#plum.promotion.promote).

Hey @pabloferz! Damn, I’m sorry to hear that. I thought this was working fine. :( Could you post a screenshot to show how it’s looking like, and perhaps the docstrings...

@francesco-ballarin The problem appears the NumPy-style docstrings. Specifically, Plum generates the following docstring for Sphinx: ``` Multiply two ints. Parameters ---------- x An int y Another int Returns ------- :...

> Hey, is there any chance of decoupling plum's doc mutations from documentation systems? @machow, definitely! Your suggestion of adding in an env variable or another kind should be simple....

@machow This is now implemented on `master`, but I'm waiting with releasing a new version until a possible `beartype` compatibility issue has been solved. I'll keep you up to date....