# Accessing com.inductiveautomation.ignition packages in Python

**URL:** <https://forum.inductiveautomation.com/t/accessing-com-inductiveautomation-ignition-packages-in-python/39702>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [October 15, 2020, 6:16am UTC](https://forum.inductiveautomation.com/t/accessing-com-inductiveautomation-ignition-packages-in-python/39702 "2020-10-15T06:16:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [October 15, 2020, 12:34pm UTC](https://forum.inductiveautomation.com/t/accessing-com-inductiveautomation-ignition-packages-in-python/39702/3 "2020-10-15T12:34:07Z")

</div>

Let me elaborate a bit:

The import behavior you were expecting corresponds to java’s `import something.something.*;`. But in java, an import is really just syntactical sugar for programmer convenience. A java programmer can always spell out full class names without any import statement.

Python/jython doesn’t work this way. In python/jython, import is a fundamental operation that makes other packages _available_ within the scope, optionally removing a package prefix or renaming the object into the new scope.

---

_[View the full topic](https://forum.inductiveautomation.com/t/accessing-com-inductiveautomation-ignition-packages-in-python/39702)._