# Import from global and project script library failing randomly **URL:** \ **Category:** Ignition\ **Created:** [July 13, 2018, 10:22pm UTC](https://forum.inductiveautomation.com/t/import-from-global-and-project-script-library-failing-randomly/18822 "2018-07-13T22:22:06Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [July 13, 2018, 10:46pm UTC](https://forum.inductiveautomation.com/t/import-from-global-and-project-script-library-failing-randomly/18822/2 "2018-07-13T22:46:16Z")
Try not importing it at all. Just call `shared.util.MWESLogging.getLog()`. Due to object lifetimes in the gateway, it is unwise to ever import anything from shared.\* or project.\*. Just use the full names wherever you need them. It shouldn't be a problem in the client either, but the designer also has weirdness. Import all you want from java. That is a pure jython operation and is effectively bulletproof. Other than the fact you can't use wildcards. See this topic: > [@Some Project Resources not publishing](http://forum.inductiveautomation.com/t/some-project-resources-not-publishing/16888/3): > > This may be a side-effect of the fact that Ignition doesn’t/can’t track the usage and retention of python code objects throughout the gateway. This means that when your script modules have interlocking dependencies, updating one script won’t impact the code objects that other scripts have imported. You may need to make a trivial change in all of your scripts and save them all together to get it to “take”. You may also need to disable then re-enable the entire project. Consider renaming the o… --- _[View the full topic](https://forum.inductiveautomation.com/t/import-from-global-and-project-script-library-failing-randomly/18822)._