# System Library Files **URL:** \ **Category:** Ignition\ **Created:** [November 7, 2019, 10:15pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773 "2019-11-07T22:15:06Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dginther](https://avatars.discourse-cdn.com/v4/letter/d/3e96dc/32.png) [@dginther](https://forum.inductiveautomation.com/u/dginther)\ **Post date:** [November 7, 2019, 10:15pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/1 "2019-11-07T22:15:06Z")
Good afternoon, Is there is an actual file location where the system library .py files are stored? ---
**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\ **Post date:** [November 7, 2019, 10:25pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/2 "2019-11-07T22:25:55Z")
When you say “the system library”, are you literally referring to the built-in system functions (`system.tag.writeBlocking`, `system.db.runNamedQuery`, etc)? They wrapped up in the various modules and JARs included in an installation, which means they’re not really accessible on the file system. If you’re talking about the various Python libraries that are included in an instillation (`urllib2.py`, `csv.py`, etc), they’re located at `%gatewayInstallDirectory%/user-lib-pylib` ---
**Author:** ![RadicalRumin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/radicalrumin/32/11543_2.png) [@RadicalRumin](https://forum.inductiveautomation.com/u/RadicalRumin)\ **Post date:** [November 8, 2019, 1:56pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/3 "2019-11-08T13:56:24Z")
> [@Paul.Scott](#): > > When you say “the system library”, are you literally referring to the built-in system functions ( `system.tag.writeBlocking` , `system.db.runNamedQuery` , etc)? They wrapped up in the various modules and JARs included in an installation, which means they’re not really accessible on the file system. Someone did make a library of mock functions, but it hasn't been updated in a while, so they may be a little outdated. > [@Ignition mock scripts on GitHub](http://forum.inductiveautomation.com/t/ignition-mock-scripts-on-github/16468): > > Hello, fellow Ignition users! As my scripting library was growing I had the need for some source code management, so I turned to using an IDE for my scripts. After trying a couple (1) I settled with PyCharm. Some of my Python scripts make use of the system.\* scripting functions, and for obvious reasons PyCharm was letting me know that those functions did not exist, so I came up with mock scripts for the system “package”, which I now release to all of you (probably) facing the same situation. … ---
**Author:** ![dginther](https://avatars.discourse-cdn.com/v4/letter/d/3e96dc/32.png) [@dginther](https://forum.inductiveautomation.com/u/dginther)\ **Post date:** [November 8, 2019, 3:18pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/4 "2019-11-08T15:18:59Z")
Yep, the built-in system functions. We were wondering if there was any way to look at them directly pretty much for the same reason as thecesrom in that link Rumin posted - which is very helpful! Thank you. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 8, 2019, 3:25pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/5 "2019-11-08T15:25:33Z")
> [@dginther](#): > > We were wondering if there was any way to look at them directly It's worth noting here that the `system.*` namespace is populated with java classes and methods constructed to work in the jython interpreter. There's no python to "look at". This is documented in the Ignition SDK. ---
**Author:** ![dginther](https://avatars.discourse-cdn.com/v4/letter/d/3e96dc/32.png) [@dginther](https://forum.inductiveautomation.com/u/dginther)\ **Post date:** [November 8, 2019, 3:42pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/6 "2019-11-08T15:42:29Z")
> [@pturmel](#): > > It’s worth noting here that the `system.*` namespace is populated with java classes and methods constructed to work in the jython interpreter. There’s no python to “look at”. This is documented in the Ignition SDK. Quite right, as Paul already mentioned. That's why I didn't mention python in my last post. I was actually going to check around in the Ignition java docs to see if I could find anything, but the link Rumin posted works. ---
**Author:** ![cesrom](https://avatars.discourse-cdn.com/v4/letter/c/ea666f/32.png) [@cesrom](https://forum.inductiveautomation.com/u/cesrom)\ **Post date:** [November 8, 2019, 4:02pm UTC](https://forum.inductiveautomation.com/t/system-library-files/29773/7 "2019-11-08T16:02:01Z")
Currently the mock library does not contain the full list of modules and functions as the actual `system.*` namespace, only the function calls that I’ve used on my projects, and new things are added as needed. If you’d like to contribute, just let me know.