Taipy GUI – Some quirks with a neat Python GUI library
Recently I have taken on the task of creating an application that required a GUI.
![Gabriel Uri](/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2F12yo38rb%2Fproduction%2Ff2b6683e8546bc42b434a3f7ced76142159573fb-500x500.png%3Fw%3D72%26h%3D72%26fit%3Dmax%26auto%3Dformat&w=64&q=75)
- Copied!
![](/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2F12yo38rb%2Fproduction%2F2a12fcf1e280824433c2603b69af5501c05a3ba8-1296x728.jpg%3Frect%3D1%2C0%2C1294%2C728%26w%3D1408%26h%3D792%26fit%3Dmax%26auto%3Dformat&w=1920&q=75)
Recently I have taken on the task of creating an application that required a GUI. Now that is an horror story of its own for someone like me, who knows the basic of Front End development but hates it and wishes it was easier.
I have used python GUI libraries in the past, like Remi, PyQt, Tkinter, but what I always wanted was something as simple as
I WANT THIS THING HERE
THIS THING SHOWS THIS AND DOES THIS
Enter Taipy, which I also recently found out that it’s a very recent library so there’s almost NOTHING about it on the internet, and it’s a great tool. That’s why I decided to write about it.
I am not going to write a tutorial on how to use it, their website has a decent documentation on how to get started. I will be documenting the difficulties and little quirks that I had to figure out about Taipy when applying it to a bigger project.
In this article![](/_next/static/media/9840756c93fa5e2f24c4484d17f96fc2.svg)
- Your code is always exposed if you don’t do something about it
- Live updating elements
- Threading
- Variable scope – an incomplete guide
![Gabriel Uri](/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2F12yo38rb%2Fproduction%2Ff2b6683e8546bc42b434a3f7ced76142159573fb-500x500.png%3Fw%3D72%26h%3D72%26fit%3Dmax%26auto%3Dformat&w=64&q=75)
- Copied!