pythonguis-examples keeps ten GUI bindings behind one main.py convention
Build desktop apps built with Python. Examples for PyQt6, PySide6, Flet, DearPyGUI, Kivy, NiceGUI, Streamlit, Tkinter, PyQt5 & PySide2
At a glance
- What is it?
- An open collection of Python GUI examples spanning PyQt6, PySide6, Flet, Kivy, NiceGUI, Streamlit, Tkinter and three more bindings, laid out one folder per library. The featured finished apps are all in the two Qt 6 bindings, there is no release history or CI, and every example still runs through the same two commands.
- Who is it for?
- Use this repository when you want working Python GUI code for a specific binding without writing the first application yourself, and pick the PyQt6 or PySide6 folder if you want the depth, since the named apps exist there in both. Pin a commit rather than tracking main, because the project publishes no releases and has no .github/ workflow directory, and expect older bindings such as PyQt5 and PySide2 to be reference copies rather than current practice.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- pythonguis/pythonguis-examples4,654 ★ · +7
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| pythonguis/pythonguis-examples | 4.6k | 4.7k |
7 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Check the selected example before installing and running it
The repository README suggests changing into an example folder, installing its dependencies with `pip3 install -r requirements.txt`, and running `python3 main.py`. Treat that as a starting point rather than a universal command: inspect the selected example's files and README first.
For example, the NiceGUI getting-started tutorial contains numbered files such as `example_001.py`, not a `main.py` in that directory. Its dependencies and launch instructions may differ from a desktop Qt demo. A desktop GUI also needs an available graphical session, while a web-based example may open a browser. The repository's Streamlit directory currently contains a README rather than a runnable example; check the current tree before relying on a particular folder.
The finished apps live in PyQt6 and PySide6, the coverage is wider
The root is one folder per library:
dearpygui/
flet/
kivy/
nicegui/
pyqt5/
pyqt6/
pyside2/
pyside6/
streamlit/
tkinter/
tools/The featured demo list, though, is a PyQt6 and PySide6 list. Every named app in it, from the web browser to solitaire, is offered in both bindings and linked twice, once under pyqt6/demos/ and once under pyside6/demos/. The README marks PyQt6 and PySide6 as having many examples, while the remaining libraries are named without that qualifier, and the closing line of that section says to pick a library and look under the demos/ folder.
So read the two statements separately. Breadth covers ten libraries, including DearPyGUI, Flet, Kivy, NiceGUI, Streamlit, Tkinter, PyQt5 and PySide2. Depth is a Qt 6 story. If you are evaluating a toolkit that is not PyQt6 or PySide6, you are browsing what exists rather than comparing finished applications, and the comparison the featured list implies is between the two Qt 6 bindings, not between all ten.
Six demos are marked QtDesigner, so the code you inherit is not all hand written
The featured entries carry small annotations that change what you get when you open the folder. Calculator, post-it notes, paint, unzip, translator and weather are each labelled QtDesigner. Currency converter is labelled PyQtGraph, and solitaire is labelled QGraphicsScene. The remaining entries carry no annotation at all.
This is more than trivia when you plan to reuse a demo. A designer built example arrives as a form definition plus generated or hand edited glue, so the interesting logic may sit in the .ui file rather than in Python, and adapting the layout means opening a designer rather than editing code. The PyQtGraph and QGraphicsScene annotations point at the rendering approach instead, which tells you those two are the ones to read if your interest is custom painting or scene based graphics. When you browse, read the folder contents before copying, because the annotation tells you the technique but not how much of the file is generated.
Sixteen apps, named after their function with a pun attached
The featured list covers the applications a Python GUI learner usually builds first, and it names each one twice: an untabbed web browser called MooseAche, a tabbed browser called Mozzarella Ashbadger, minesweeper as Moonsweeper, notepad as No2Pads, a calculator as Calculon, a word processor as Megasolid Idiom, a webcam and snapshot tool as NSAViewer, a media player as Failamp, post-it notes as Brown Note, a paint app as Piecasso, an unzip utility as 7Pez, a translator as Translataarrr, a weather app as Raindar, a currency converter as Doughnut and solitaire as Ronery.
The naming is worth noting because the folder names are the plain words underneath, so browser, browser_tabbed, minesweeper, notepad, calculator, wordprocessor, camera, mediaplayer, notes, paint, unzip, translate, weather, currency and solitaire are the paths you will actually type. Two of them also carry a scope hint: the browser exists in two variants, untabbed and tabbed, and the camera entry is about a webcam and snapshot rather than a photo viewer. Several of the featured apps also have step by step build write-ups, so a demo folder can be either a finished program or the last state of a tutorial you can retrace.
Contributions follow a three part folder path
The contribution rule is short enough to state exactly: fork the repository, add your example code files in the [library]/[type]/[folder-name] shape, and open a pull request. That path convention is the same one the existing tree follows, with the library as the first segment and the type as the second, which is what keeps ten toolkits in one repository without them colliding.
The repository describes itself as an open collaborative collection of UI demonstrations, tutorials and examples, with new additions welcome, and it is explicit that examples can be freely re-used, re-mixed and tweaked.
No releases, no CI, and the last push predates the newest bindings
The repository publishes no GitHub releases, so there is no version to pin and no changelog to read, and the last push to the default branch landed on 2026-03-19. The top level holds .gitignore, LICENSE, README.md, the library folders and tools/, with no .github/ directory and therefore no workflow running the examples. Nothing in the repository checks that an example still launches after a toolkit release.
The consequence for anyone depending on this code is practical. Treat a specific commit as your reference point rather than tracking main, because a library update can change an import or a widget API and you would have no signal from this repository that an example broke. The oldest folders deserve the most caution: PyQt5 and PySide2 are previous generation bindings kept alongside the current ones, so read them as reference implementations rather than as current advice. For the same reason, prefer the PyQt6 or PySide6 folder when you want the code most likely to line up with a toolkit you would install today.
The examples and the tutorials are two views of the same code
Reading the repository as a code drop misses half of its design. Alongside the demos it holds step by step tutorial code taken from pythonguis.com, and the two are linked to each other rather than kept apart: an example file points back to its tutorial, and a tutorial points forward to the runnable example. Many examples carry more detailed write-ups on the site, and the README says the links to specific tutorials live in the source code of the example, so the trail starts in the repository and ends in prose.
That structure also answers the question the repository asks of newcomers who have not picked a toolkit. For somebody starting from zero there are introductory PyQt6 and PySide6 tutorials linked from the README, and for somebody who has not chosen between libraries there is a separate guide on the site framed as which Python GUI to use. Both routes end in code you can run here.
The practical effect on your own workflow is that a folder can be read two ways. If you want to understand a pattern, follow the tutorial link inside the example file. If you want to see a working program, run main.py and change it. Neither reading requires anything beyond the two commands in the getting started steps.
Editorial conclusion
Use this repository when you want working Python GUI code for a specific binding without writing the first application yourself, and pick the PyQt6 or PySide6 folder if you want the depth, since the named apps exist there in both. Pin a commit rather than tracking main, because the project publishes no releases and has no .github/ workflow directory, and expect older bindings such as PyQt5 and PySide2 to be reference copies rather than current practice. For choosing between libraries, the project's own guide is a better starting point than the folder names.
Frequently asked questions
What is Python Guis?
Python GUIs is the project behind this example repository and the pythonguis.com website, both by Martin Fitzpatrick. The repository holds hundreds of Python GUI examples for PyQt6, PySide6, Flet, DearPyGUI, Kivy, NiceGUI, Streamlit, Tkinter, PyQt5 and PySide2, with step by step tutorial code taken from the site.
How do I run an example from pythonguis-examples?
Change into the example's folder and install its requirements with pip3 install -r requirements.txt, then start it with python3 main.py. Every example in the repository ships a file called main.py as its entry point.
Which Python GUI libraries does pythonguis-examples cover?
Ten bindings, each with a top level folder: PyQt6, PySide6, DearPyGUI, Flet, Kivy, NiceGUI, PyQt5, PySide2, Streamlit and Tkinter. The README describes PyQt6 and PySide6 as having many examples.
How do I add my own example to pythonguis-examples?
Fork the repository, add your example code files under the [library]/[type]/[folder-name] path, and open a pull request. The README asks contributors to keep the same folder shape used by the existing tree.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pythonguis-pythonguis-examples)Star history chart for your README
[](https://hysenlabs.com/projects/pythonguis-pythonguis-examples)Was this useful?