# \[IGN-6503\]Project Library Script Initialization Races

**URL:** <https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [November 14, 2024, 8:51pm UTC](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636 "2024-11-14T20:51:28Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![Clancy\_Cavanaugh](https://avatars.discourse-cdn.com/v4/letter/c/45deac/32.png) [@Clancy\_Cavanaugh](https://forum.inductiveautomation.com/u/Clancy_Cavanaugh)\
**Post date:** [October 22, 2025, 8:00pm UTC](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636/23 "2025-10-22T20:00:11Z")

</div>

Importing from project library scripts is known to cause problems. Instead of importing you should be using the full path/name of the resource you would normally import.

```python
# Don't use import
from shared.x import y
# instead call it as
shared.x.y()

```

> [@Import from global and project script library failing randomly](https://forum.inductiveautomation.com/t/import-from-global-and-project-script-library-failing-randomly/18822/2):
>
> 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:

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636)._