# Input() in python and Tracis CI code analyse

**URL:** https://travis-ci.community/t/input-in-python-and-tracis-ci-code-analyse/3664
**Category:** Travis CI Discussions & Feedback
**Created:** [June 8, 2019, 10:58pm UTC](https://travis-ci.community/t/input-in-python-and-tracis-ci-code-analyse/3664 "2019-06-08T22:58:56Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [December 3, 2019, 2:24am UTC](https://travis-ci.community/t/input-in-python-and-tracis-ci-code-analyse/3664/3 "2019-12-03T02:24:30Z")

</div>

See

> [@User input during the Travis built](https://travis-ci.community/t/user-input-during-the-travis-built/5502/2):
>
> There is no way to interact a human with the build while it is running; CI is meant to be automated, not interactive. You can simulate certain user interactions with many tools, such as a simple echo "ANSER" | cmd and [expect](https://core.tcl-lang.org/expect/index).

This is the same issue.

---

_[View the full topic](https://travis-ci.community/t/input-in-python-and-tracis-ci-code-analyse/3664)._