Caleb Hattingh

@mocobeta This example at mkdocs shows integration of pdoc into a mkdocs build: https://github.com/mitmproxy/pdoc/tree/main/examples/mkdocs/ There is a comment that says: > [mkdocstrings](https://mkdocstrings.github.io/) is a great alternative to pdoc if you...

I tried a few things, and it seems that mkdocstrings doesn't do a good job of pulling out the docstrings from the rust source. So I guess that means pdoc...

@pawamoy I guess the mkdocstrings is not using that feature then. It would likely be a high value improvement if you could help them to make it work with dynamic...

That's good feedback, thank you for looking into this 😄 . This is the correct issue IMO. I'll try to find some time to fix up the module references next...

I added a PR here to fix only the module declarations: https://github.com/quickwit-oss/tantivy-py/pull/190. After that is merged I will return to make a second PR using your example showing the mkdocstrings...

I've added all the lindera features, and also an interface to specify configurable options on registration. The code is still rough, for example I need to rename quite a few...

It would be much nicer to provide this as an additional package that can be installed. The lack of a stable ABI prevents this, unless we wrap up the Lindera...

Just thinking out loud, we could consider adding some kind of new `ExternalTokenizer` tokenizer, create an instance that encapsulates another tokenizer with a C interface, and that separate tokenizer is...

Must be something in the water, because this got published just yesterday. Many projects dealing with the plugin problem: https://www.arroyo.dev/blog/rust-plugin-systems

Ok so the reason I haven't moved forward with this is because I want to explore different solutions that allow a user to pip install additional tokenizers and register them...