How to generate documentation for Python-side of library? #1039
-
I'm not sure if this is right place to ask, but I'm kind of lost rn and I was hoping someone could help out. Anyway, so my library is exposed via both a Rust and Python library, and the Rust side for documentation was easy peasy, just publish to crates.io and their systems handled the rest. But I'm kind of lost at how I should generate my docs for the Python side of things. I've loosely heard of Read the Docs, and I tried dabbling with both Sphinx and mkDocs earlier, but I didn't get much of anywhere. Is there any known system that I can use to generate my docs automatically in a fashing similar to how If it helps at all you can find my current project at https://github.com/makedeb/makedeb-srcinfo. Thanks a ton for this and PyO3 btw too :), it made developing a library for both ecosystems extremely easy, I don't think I put more than 30 minutes (if that) on getting the Python side of my library to just work flawlessly. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Have you tried https://maturin.rs/sphinx.html? |
Beta Was this translation helpful? Give feedback.
-
I took another shot at this today after a bit of it not working, and it's just working now, no clue why :p. Anyway, looks like I'm set now, thanks a ton! |
Beta Was this translation helpful? Give feedback.
I took another shot at this today after a bit of it not working, and it's just working now, no clue why :p. Anyway, looks like I'm set now, thanks a ton!