# Import error: no module named os

**URL:** <https://forum.inductiveautomation.com/t/import-error-no-module-named-os/6223>\
**Category:** 3rd Party Modules\
**Created:** [April 13, 2013, 3:31pm UTC](https://forum.inductiveautomation.com/t/import-error-no-module-named-os/6223 "2013-04-13T15:31:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chuckcoughlin](https://avatars.discourse-cdn.com/v4/letter/c/e19b73/32.png) [@chuckcoughlin](https://forum.inductiveautomation.com/u/chuckcoughlin)\
**Post date:** [April 13, 2013, 3:31pm UTC](https://forum.inductiveautomation.com/t/import-error-no-module-named-os/6223/1 "2013-04-13T15:31:35Z")

</div>

I thought I’d post a solution in case anyone else happens to run into this. This issue has plagued me for months. Whenever I tried to access the ‘os’ module in Ignition, I’d get this error.

Turns out that I had previously used my system for Android development and had a JYTHONPATH variable set pointing into the Android SDK (which doesn’t include os).

–chuck