# Displaying console in exported executable output

**URL:** <https://discourse.processing.org/t/displaying-console-in-exported-executable-output/15816>\
**Category:** Processing.py\
**Created:** [November 25, 2019, 9:12pm UTC](https://discourse.processing.org/t/displaying-console-in-exported-executable-output/15816 "2019-11-25T21:12:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![GoToLoop](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/gotoloop/32/86_2.png) [@GoToLoop](https://discourse.processing.org/u/GoToLoop)\
**Post date:** [November 26, 2019, 4:08am UTC](https://discourse.processing.org/t/displaying-console-in-exported-executable-output/15816/2 "2019-11-26T04:08:17Z")

</div>

> [@katesfb](#):
>
> So is it possible to view the console window output when running a Python Mode script as an exported executable?

PDE (Processing’s IDE) got its own console, which isn’t the same as the OS console 1.

I tried to redirect `print` to the real ` __stdout__ ` console but it didn’t work on the win console:  
`print >> sys. __stdout__ , 'Am I displayable?'`

But when I tried Git’s bash, everything got displayed there!

And no ` __stdout__ ` was needed. Vanilla `print` just works:  
`print 'Am I displayable?'`

And Git’s bash also works on exported Java Mode sketches!

Just be aware that Git’s bash, just like any Unix bash, we need to prefix current directory files w/ `./` before its name.

For example, if we wanna run the filename “Hints.exe” on current folder, we type in: ./Hints

Grab Git install from this site: [Git-Scm.com](http://Git-Scm.com)

---

_[View the full topic](https://discourse.processing.org/t/displaying-console-in-exported-executable-output/15816)._