# \[Scripting\] In-editor documentation for 3rd party libraries

**URL:** <https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [September 29, 2025, 7:46pm UTC](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072 "2025-09-29T19:46:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [September 29, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072/2 "2025-09-29T20:08:56Z")

</div>

> [@Script Library Formatting and Documentation](https://forum.inductiveautomation.com/t/script-library-formatting-and-documentation/82056/3):
>
> If you're on 8.1.19 or higher, project library scripts with "docstrings" per Python convention do show up in the autocomplete in other editors: [https://docs.inductiveautomation.com/display/DOC81/Scripting+in+Ignition#ScriptinginIgnition-SystemFunctions,Hints,andAutocomplete](https://docs.inductiveautomation.com/display/DOC81/Scripting+in+Ignition#ScriptinginIgnition-SystemFunctions,Hints,andAutocomplete) If you're on 8.1.32 or higher, if you author those docstrings according to Google's Python style guide, you'll even get nice argument and return value descriptions.

@paul-griffith may have a different answer, but as far as I know it should work so long as you follow the convention.

---

_[View the full topic](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072)._