# Perspective, time.sleep vs later.py

**URL:** <https://forum.inductiveautomation.com/t/perspective-time-sleep-vs-later-py/39955>\
**Category:** Ignition\
**Created:** [October 23, 2020, 12:29pm UTC](https://forum.inductiveautomation.com/t/perspective-time-sleep-vs-later-py/39955 "2020-10-23T12:29:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 23, 2020, 2:59pm UTC](https://forum.inductiveautomation.com/t/perspective-time-sleep-vs-later-py/39955/2 "2020-10-23T14:59:13Z")

</div>

`time.sleep` should be avoided in basically every scenario - the only exception I would _maybe_ give is a dedicated thread spawned by `invokeAsynchronous`. `later.py` technically hooks into an internal class, but the signature of that class is pretty unlikely to change, and, crucially, it _does not_ require a thread to be kept sleeping.

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-time-sleep-vs-later-py/39955)._