Sphinx will have better support for multi-line python signatures.

[2bndy5]

I was just notified of an error when building with Sphinx (master branch):

Exception occurred:
  File "/home/mg/git/sphinx/sphinx/domains/python.py", line 575, in handle_signature
    signode += _parse_arglist(arglist, self.env, multi_line_parameter_list)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: _monkey_patch_python_parse_arglist.<locals>.parse_arglist() takes from 1 to 2 positional arguments but 3 were given

This stems from https://github.com/sphinx-doc/sphinx/commit/86b07d4a97a225e79150d14e25a768ebc4c087cc

Concerns the monkey_patch for default values to args: https://github.com/jbms/sphinx-immaterial/blob/f5e3213c511e4960aa5b4758b92de4652d1807c0/sphinx_immaterial/apidoc/python/style_default_values_as_code.py#L9-L16

[2bndy5]

This specific to sphinx v7.1.0

[pradyunsg]

FWIW, the Sphinx-side changes influence C, C++, JS and Python.

[jbms]

I think we will at least need some css changes to just directly support this option.

This theme has two forms of signature line wrapping:

• a simple parameter wrapping that is similar to the feature added to shinx, although implemented with css rather than by inserting dl tags. In practice this works well enough for Python and probably c, but doesn't work that well for c++ which has more complicated signatures.
• wrapping based on clang-format

They are basically independent, so we could remove the simple wrapping and leave the clang-format wrapping.

Our feature does have the advantage that it can be more selectively applied since it is configured using our object description options mechanism.

[2bndy5]

we could remove the simple wrapping and leave the clang-format wrapping.

I'm leaning towards this idea. Better to rely on functionality in sphinx than maintain our hacky (monkeypatched) workaround with CSS.