# Documenting Python Libraries with 3rd Party Tools **URL:** \ **Category:** Ignition\ **Tags:** scripting, ignition80\ **Created:** [June 16, 2022, 6:52pm UTC](https://forum.inductiveautomation.com/t/documenting-python-libraries-with-3rd-party-tools/60850 "2022-06-16T18:52:40Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [June 17, 2022, 5:19pm UTC](https://forum.inductiveautomation.com/t/documenting-python-libraries-with-3rd-party-tools/60850/2 "2022-06-17T17:19:08Z")
Nothing useful to add, except that I was facing similar issues while goofing around with type annotations and mypy. > [@Running mypy or other static type-checking on Ignition Jython scripts](https://forum.inductiveautomation.com/t/running-mypy-or-other-static-type-checking-on-ignition-jython-scripts/60799): > > On Python projects unrelated to Ignition, I’ve been starting to use type annotations and static type checking tools like [mypy](http://mypy-lang.org/). I find the type annotations very helpful as reminders of what function parameters are supposed to be, and mypy helps find corner cases that would’ve lead to exceptions. If you’ve never seen type annotations in Python, the mypy cheat sheets are the simplest demonstration and practical explanation I’ve found. Annotations used to be stored as comments in [Python2](https://mypy.readthedocs.io/en/stable/cheat_sheet.html), but Pytho… Didn't come up with any good solutions (yet), but I haven't stopped trying. This is just a "would be nice to have" feature in our setup, so I haven't been able to dedicate much time to it. --- _[View the full topic](https://forum.inductiveautomation.com/t/documenting-python-libraries-with-3rd-party-tools/60850)._