OK, #python question: How do I generate docs for an embedded python project that uses a #SWIG generated library? #pydoc #pdoc and the like rightly complain about non-existent modules, but all the information I want is contained in docstrings and type annotations, so it *should* be possible to generate docs right?

Is there a tool for this?

I added a few pages to #Griffe's docs: alternative projects, downstream projects, and built-in/official/third-party extensions.

Very cool projects mentioned in there! #Docspec, #pdoc, #papyri, #quartodoc, etc. And I discovered a few Griffe extensions in the process, it's awesome

- https://mkdocstrings.github.io/griffe/alternatives/
- https://mkdocstrings.github.io/griffe/downstream-projects/
- https://mkdocstrings.github.io/griffe/extensions/built-in/

Why are the documentations of tools that are meant to create documentations so terrible? #pdoc #sphinx #python

If you are looking for a nice way to document your Python project, you should really have a look at pdoc maintained by the incredible @max - it works, it's convenient and very practical.

Don't be confused by pdoc3 which is a crappy fork and should be discarded.