# Python API documentation?

**URL:** https://discourse.slicer.org/t/python-api-documentation/12298
**Category:** Development
**Tags:** python, documentation, api
**Created:** [June 30, 2020, 1:24pm UTC](https://discourse.slicer.org/t/python-api-documentation/12298 "2020-06-30T13:24:18Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [June 30, 2020, 3:04pm UTC](https://discourse.slicer.org/t/python-api-documentation/12298/2 "2020-06-30T15:04:53Z")

</div>

Good point - we discussed this [at the developer hangout](https://discourse.slicer.org/t/2020-06-30-hangout/12286) and there isn’t a great universal solution given how many libraries slicer builds on an integrates. [Here’s a very old page](https://www.na-mic.org/wiki/AHM2012-Slicer-Python) that lists and links back to the various pieces.

We also noticed that while Qt’s Python documentation is good, it’s not perfect either. For example this [python documentation](https://doc.qt.io/qtforpython/PySide2/QtWidgets/QLabel.html#PySide2.QtWidgets.PySide2.QtWidgets.QLabel.linkActivated) just lists the method type, while the [corresponding C++ documentation includes useful text](https://doc.qt.io/qt-5/qlabel.html#linkActivated).

It would be great if someone wants to build a better doc infrastructure, but for now I suggest looking at the source code. And of course you can use `help` in the python interactor.

Hope that helps

---

_[View the full topic](https://discourse.slicer.org/t/python-api-documentation/12298)._