Sergei Izmailov

I don't have an answer for that. I did a minimal change that worked for my use case. I wanted separation of exceptions because of their lesser importance than regular...

This PR does not have `entry_points.console_scripts` in `setup.cfg`. it would be nice to have aliases for `documentation/python.py` like `mcss-python` (+ same for doxygen).

IMO `documentation` is essential part of mcss and should be included in package whatever it takes. You are right that turning `documentation` into a proper python package probably should be...

This PR is marked as draft primarily because it *unconditionally* adds extra entries to search index without possibility retain older behavior. It might be undesirable for some users. I'm not...

My use case is close to any word search:  I agree, search result gets bigger and it makes harder to navigate through. Results sort algorithm needs an adjustment for...

Indeed, with this PR magnum docs hits limits just like in #123 even with changes from `search-32` branch, so this is definitely not a perfect/uniform solution.

Filtering mechanism is a nice feature! The only thing I want to add is ability to combine two or more filters together, i.e. make interface composable. > #155 can't be...

@AWhetter Would it be less intrusive to make sphinx and stubgen support pybind11 overloading syntax? FYI: A set of changes to stubgen is on the way: https://github.com/python/mypy/pull/9903

Ok, that seems reasonable. What about signatures that span multiple lines? Presumably pybind11 would always produce exactly one signature per line, but we are talking about 3rd party tools too....

The sphinx choice of trailing backslash as indication for multiple signatures become fairly unfortunate one. It might result into a cumbersome signature parsing implementation which supports both "legacy" and "new"...