# \[Scripting\] In-editor documentation for 3rd party libraries **URL:** \ **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:** 4\ **Page:** 1
**Author:** ![Tyler\_McLean](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Tyler\_McLean](https://forum.inductiveautomation.com/u/Tyler_McLean)\ **Post date:** [September 29, 2025, 7:46pm UTC](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072/1 "2025-09-29T19:46:44Z")
Perhaps there is already a solution to this or a forum post I just didn’t see when I was searching for this, but is there a way to view the pydoc documentation of 3rd party python libraries added into Ignition the same way that 3rd party java scripting modules show up in the editor? I’d even be willing to generate the .properties files similarly. I have a library I’m working on that we will be able to use in multiple projects/stations that share a lot of repeated business logic. I’d like to be able to hand this off to our engineering teams so that they can build the smaller scale stuff without bugging my IT team but they’ll need documentation. I can always generate it out-of-band and host it somewhere internally but I’d prefer to have it in the environment they’re writing the scripts in if possible to keep them from getting frustrated when they need to use a new function. Any help is appreciated Thanks, Tyler ---
**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")
> [@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. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [September 29, 2025, 9:23pm UTC](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072/3 "2025-09-29T21:23:00Z")
Basically unchanged since 8.1.whatever when we added docstring parsing. It works for your _project_ library, but not the third party library that's only accessible on disk, which is what I think the OP was talking about. There are no short term plans to do that, @Tyler_McLean. It's on a long term roadmap, but may end up superseded by other work to just enable external code editors to work with the designer completely. ---
**Author:** ![Tyler\_McLean](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Tyler\_McLean](https://forum.inductiveautomation.com/u/Tyler_McLean)\ **Post date:** [September 30, 2025, 11:54am UTC](https://forum.inductiveautomation.com/t/scripting-in-editor-documentation-for-3rd-party-libraries/111072/4 "2025-09-30T11:54:58Z")
Thanks for the answer Paul. It is as I expected then. All good! I’ll just create the documentation separately then and patiently await the day an external editor like PyCharm works with the designer