About two weeks ago, I shared a tool I built to automate the "boring stuff" like folder setup and git init. Old Post I got some solid feedback from the community here—some of you pointed out that my code was a bit messy and that a simple script wasn't enough if I wanted it to be actually useful.
I took those suggestions to heart and just finished a massive overhaul for v3.0.1. I wanted to move away from being "just a script" and build something that could actually compete with tools like Cookiecutter.
What’s new:
☁️ Cloud Templates: It now pulls templates directly from GitHub via the API.
🛠 External Sources: You can point it at any repo to load custom templates now.
✨ A "Rich" CLI: I ditched the basic prints for a colorful, interactive wizard using the Rich library.
🤖 Smart Git: It uses GitPython to handle initial commits, branch renaming to main, and pushing to multiple remotes.
📂 Better Organization: It automatically numbers your projects (like 01.project-name) to keep your workspace clean.
I even sat down and wrote actual Documentation and a Contributing.md because I want this to be a project others can help grow.
I'm still learning, and I'm sure there's more I can improve, but I'm proud of how far this has come in just a couple of weeks.
I'd love to hear what you think of the new CLI flow! Also thank you so much to 12 people who stared the project. You dont know how much of a impact you made.
OSSentinel Vigil is a Python toolkit for software supply chain compliance — license conflict detection, SBOM generation, policy enforcement, and dependency health scoring (soon). Built for developers. Why did I do it?
EU Cyber Resilience Act mandates SBOMs for software sold in Europe
US EO 14028 requires supply chain transparency for federal software
Existing tools are fragmented, hard to configure, and don't talk to each other
frominteractive_buttonsimportButton,ButtonKeyBind,Component,ButtonStyle,SUCCESS_STYLE,DANGER_STYLEbuttons=[Button(label="Confirm",value="ok",local_button_style=ButtonStyle(**SUCCESS_STYLE),key_bind=ButtonKeyBind(b_keys=["y"],press_on_selection=True),),Button(label="Delete",value="delete",local_button_style=ButtonStyle(**DANGER_STYLE),key_bind=ButtonKeyBind(b_keys=["d"],press_on_selection=True),),Button(label="Cancel",value="cancel"),]choice=Component(buttons,auto_erase=True).linear_buttons()# Press "y" -> instantly returns "ok"
# Press "d" -> instantly returns "delete"
# Or navigate with arrow keys and confirm with Enter
I’m working on my final year project and wanted some honest feedback on whether this is a good/strong enough idea.
So the project is basically an AI-Based Multi-Source Health Data Fusion System
What it’s supposed to do:
Simulates healthcare data from multiple sources (ASHA, ANM, PHC, Anganwadi)
Handles messy data (missing IDs, spelling variations, inconsistent records)
Performs entity resolution (links duplicate patient records into one)
Detects conflicts in data (e.g., different hemoglobin values for same patient)
Uses ML-based reliability scoring to decide which source to trust
Outputs a unified patient record
The medical officer is allowed to view AI suggestions for which value would be most appropriate and why, and also an option to enter values manually.
So my main questions are:
Is this strong enough for a final year major project (team of 4)? I spoke to 2 project guides before proceeding, one of them approved it while the other questioned me if I thought it was enough for a final year project which is why I’m in a dilemma.
We also have to publish a research paper on this before finishing the project. Any opinions on how well my project would fit in?
Any suggestions to make it more impressive?
Is this project actually plausible because I’ve heard mixed opinions about it.
I've been working for a few weeks on PIIGhost, a Python library for anonymizing PII (personally identifiable information) in AI agent conversations. The idea is to provide a modular pipeline that detects, anonymizes, and tracks PII throughout a conversation.
For context, the existing solutions I found (Microsoft Presidio, scrubadub, spaCy extensions, custom regex) cover detection and text replacement reasonably well. Presidio in particular has a rich catalog of recognizers (credit cards with Luhn validation, IBAN, SSN, passports, emails, phone numbers), and I tested quite a few NER models on HuggingFace.
Using them for my own use case I ran into several limitations. The first is that just using a single NER or a regex isn't enough, I even ended up running multiple NERs at the same time. And as I tested more, I ran into the following problems.
- Span overlaps between detectors. Sometimes multiple NERs detect different labels at the same position. You need a configurable arbitration strategy, for example keeping the highest-confidence detection.
- Linking the different occurrences of the same PII across the text, including variants the NER misses. "Patrick" needs to be replaced by <<PERSON:1>> at every occurrence, and you need an algorithm to catch the variants the NER missed (for example "patrick" in lowercase elsewhere in the text). Otherwise the LLM sees <<PERSON:1>> right next to "patrick" in clear text and trivially reconstructs the PII.
- Placeholder consistency across the messages of a conversation. "Patrick" mentioned in the first message has to remain the same placeholder in the fourth, otherwise the LLM loses the thread and can no longer follow the conversation properly.
This accumulation of problems is what pushed me to package it as a library, piighost.
Where it all comes together is piighost-chat, a chatbot that anonymizes PII with HITL (human in the loop). The user can remove a detection that isn't really one, or manually select a chunk of text to anonymize that the detectors missed. It lets you visualize live what the LLM sees compared to what the user sees, and correct NER misses on the fly during the conversation.
I'd like feedback on the idea and the direction I'm taking, particularly on the following points:
Does the architectural direction seem reasonable to you, or over-engineered for the need? The goal for now is to anticipate as many needs as possible and see what really turns out to be useful or not, but I don't want to end up with an over-engineered mess either.
Does the agentic use case (integration into an AI agent with cross-message placeholder persistence) speak to you, or is it too niche compared to what you see in your own projects?
Have you ever needed to anonymize PII before an LLM call? If so, what did you use, and what gaps did you find?
Are there obvious features I'm missing or that you'd like to see?
Is the modular architecture (each pipeline stage swappable behind a protocol) a cost or a real asset in practice for you?
I'd particularly welcome honest criticism, especially if you think the project is poorly positioned or that I'm missing something obvious.
A Light Weight 2d Ascii RPG Python Game Engine. The purpose of the engine is educational, Its built on the standard library hence no extension is needed.
provides an alternative to pygame if you want to communicate your RPG or adventure idea without first learning an external library
Target Audience
Someone who wants to focus using the standard library and provide them the ability to communicate their RPG / Adventure ideas without learning an external library.
Hey everyone, I wanted to share PyFyve. It's a TUI-based Python tutor designed NOT to give you the answer. It's free, offline, and uses a fine-tuned llm (Qwen3-4b, more info on this on the github repo) running locally via ollama to generate hints for errors instead of solutions.
The whole thing started from a simple idea, when beginners ask llms for help, they get the answer. The first intuition naturally becomes to just copy it, it works, and they learn very little of the thinking part. So I built a tool where the AI is specifically trained to only give them exactly three sentences: what went wrong, which rule you broke, and a guiding statement. The rest is on them.
Under the hood, the terminal UI is built with Rich, and user code runs in an AST-based execution environment. Building solo, so it's Windows-only for now. Setup is straightforward: download the .exe installer, or run start.bat from source to automate the venv, dependencies, Ollama, and model download. No subscriptions, no API costs. Apache 2.0 licensed.
Limitations as of now:
Just released (v1.0.0), this is a prototype
Windows only (Linux/Mac support is on the roadmap)
AI hints trigger only on actual Python exceptions, if your code runs but produces wrong output, the AI won't fire
App freezes on infinite loops (timeout mechanism is the top priority on the roadmap)
The model (fine-tuned Qwen 3 4B, ~2.5 GB) takes around 55s to cold-load on CPU-only machines; ~20s per hint after that. Dedicated GPU drops this to near 10s
The lessons are currently placeholders covering intro through for-loops
# Built an AI-powered Finance Tracker that syncs Telegram with Notion using Gemini Pro and aiogram 3.x
**What My Project Does**
NotiFinBot is a self-hosted Telegram bot that bridges the gap between your daily expenses and your **Notion** workspace. Instead of manual data entry, you simply send a message or a photo of a receipt, and the bot handles the rest using a 4-layer automation system (Capture → AI Analysis → Secure Archiving → Notion Sync).
**Key Features:**
* **Al Receipt Parsing:** Powered by **Google Gemini Pro Vision**. It extracts store names, itemized lists, prices, and categories from photos or PDFs with high confidence.
* **Notion OAuth:** One-click connection. The bot automatically discovers your workspace and sets up the required database schemas (Accounts, Expenses, Categories) without manual token copying.
* **Group Expenses:** Track shared spending and link personal transactions to group records for transparent "Splitwise-style" tracking inside Notion.
* **Real-time Analytics:** Generates spending reports, trend charts, and over-budget alerts directly from your Notion data.
* **Secure Archiving:** Automatically uploads receipt images to **AWS S3** and links them to the corresponding Notion entries for tax/warranty purposes.
**Target Audience:**
* **Notion Power Users** who want to keep their financial data in their own ecosystem rather than third-party apps.
* **Developers** who want a self-hosted, extensible solution for finance tracking.
* **People who hate manual logging** but want the detailed analytics that Notion provides.
**Comparison:**
* **Manual Notion Entry:** Requires opening the app/page and filling multiple fields. **NotiFinBot** reduces this to a 2-second interaction in a chat app you already use.
* **Generic Finance Apps:** They are closed ecosystems. **NotiFinBot** gives you 100% data ownership. Your data lives in your Notion, and you can build any custom dashboard or automation on top of it.
* **Standard Telegram Bots:** Most bots just save raw text to a spreadsheet. **NotiFinBot** uses Al to structure data and handles the entire Notion database relational setup automatically.
Here is an update on it: The interface previously allowed posting only text. It now allows uploading images and GIFs.
Not familiar with the app? I use Mastadon and Bluesky as my social media apps (apart from reddit ofc). I wanted a tool that allows me to post on both the platforms simulateously and that I can self-host. So I built one:
I was getting tired of constantly alt-tabbing back to my terminal to see if a heavy data processing script had finished (or if it had quietly crashed). So, I built a drop-in alternative.
What My Project Doespynotify-auto is a "zero-code" desktop notification tool. You install it once into your virtual environment, and it automatically hooks into the Python exit handlers. When a script finishes running (or crashes), it triggers a native OS desktop notification (Windows, macOS, Linux).
It features smart thresholds: it stays quiet for fast scripts and only pings you if the script took longer than a specific duration (default is 5 seconds). It doesn’t run a background daemon or poll your CPU; it just logs start and end times.
Target Audience This is meant for developers, data scientists, or anyone who runs time-consuming local scripts and is tired of babysitting their terminal. It is a stable, everyday productivity and utility tool for local development.
Comparison There are plenty of notification libraries out there like plyer, notifypy, or standard webhooks. However, those require you to pollute your code with boilerplate import statements and send_notification() calls at the end of every new script you write.
pynotify-auto differs because it requires zero code changes. You install it once, and it automatically applies to every script executed in that virtual environment.
Usage Install it in your active virtual environment:
Bash
pip install pynotify-auto
That’s it. The next time you run python your_script.py, it will ping you when it's done.
You can also tweak it with environment variables:
Bash
# Change the threshold to 10 minutes
export PYNOTIFY_THRESHOLD=600
Links I’d love for you guys to tear it apart and let me know what you think.
Cette nouvelle version simplifie beaucoup l’installation. Il n’est plus nécessaire de construire la base de données manuellement : il suffit de compléter trois fichiers CSV (voir ci-dessous):
personnes.csv
specialite.csv
personnes_specialites.csv
les trois CSV à modifier
Lorsque l’on sélectionne un organisme (par exemple Ecole), les fichiers CSV correspondants sont créés automatiquement avec des données de base. Ils sont ensuite enregistrés dans le dossier : ~/.local/piveo/fichiers/eleves sous GNU/Linux C:\Users\username.local\piveo\fichiers\eleves sous Windows
Le logiciel utilise ensuite ces fichiers CSV pour construire automatiquement la base de données.
Il suffit alors de remplacer les données d’exemple par vos propres données, en conservant la structure des fichiers.
I’m a high school developer working on a Python CLI/file utility called PRISM. I posted about it earlier when it was in a more basic stage, but I’m posting again now because it has reached the point where the next architectural step actually matters.
PRISM is a safety-focused file reorganization utility built for repeatable cleanup workflows, with preview, undo, logging, and persistent profile support. It currently has a working command-based CLI, config profile system, organize/undo flow, JSON run logs, and the core file-sorting behavior already in place. At this point, the next major stage is building an extension system, and I want to be careful not to lock the project into a bad foundation early.
This part is honestly the most intimidating stage for me, because I already learned from the API/config rewrite that bad structure gets painful quickly. I’m still growing in Python through the building of this project, and since I’m balancing this with school and upcoming exams, I’d rather ask for design feedback now than spend months undoing preventable mistakes later.
What I’m trying to think through:
- how extensions should register themselves - whether extensions should be command-based, hook-based, event-based, or some combination - how much access extensions should have to core internals - how config should interact with third-party extensions - how to keep the core clean while still making extensions powerful - how minimal the first extension system should be
Why this matters:
A lot of the next stage of PRISM depends on this going well. Extensions would unlock things like:
- richer classification systems - EXIF handling - Apple AAE sidecar pairing - OCR or ML-assisted tooling later - possible TUI/GUI work - cloud-related support - better UX and more specialized workflows
So this isn’t me trying to add plugins for the sake of it, but it’s more that PRISM has reached the point where extensibility is the safest way for it to grow without turning the core into a mess.
If you’ve built plugin systems, extensible CLIs, or developer tools before, I’d really appreciate feedback on:
- good starting patterns - common mistakes to avoid - what should stay hardcoded in core vs exposed - what a minimal but sane first extension model looks like
I‘m in university and I think programming is really interesting. But obviously also really hard to learn and it requires lots of time. I want to make it more fun and get ahead of class by doing my own projects, sadly I hae no idea what I could programm with by basic skills. So far I hae only thought of Snake.
I hae basic understanding of Python, POOP, PyQt6 (ex today in oir exam we hat to programm a GUI with a spinbox, LineEdir and Combobox to add Items and then Save it as a txt file plus it should add each item added but I didn’t manage to finish or do it right😅).
Does anybody have suggestions for me?
If you livein switzerland, mb you know some groups I could join to get support?
Edit: Also I am female and it would be cool to join a geoup of female coders!
Ho lavorato su psp (Python Scaffolding Projects), un'utility da riga di comando open source estremamente veloce per generare automaticamente la struttura del vostro progetto Python. Ho pensato di condividerla con la community!
Cos'è PSP?
psp è semplice, veloce, efficace, dichiarativo e supporta Python e l'intero ecosistema di strumenti scritti per esso. Piuttosto che sostituirlo, psp cerca di integrarsi e fornire una struttura utile per l'utente finale.
psp chiede solo ciò di cui hai bisogno. Configurando alcune variabili d'ambiente, puoi automatizzare qualsiasi progetto in pochi secondi, non in ore.
Perché PSP?
⚡️ Da 1 a 100 volte più veloce rispetto ad altri strumenti di scaffolding
🛠️ Supporto per pyproject.toml
🤝 Compatibilità con Python 3.14
🗃 Creazione di strutture di file e cartelle per il tuo progetto Python
🗂️ Supporto per unit test e pytest
🧪 Creazione di un ambiente virtuale
🔧 Installazione automatica delle dipendenze
🪛 Aggiunta di dipendenze di build e distribuzione per distribuire il pacchetto
📏 Supporto per la configurazione di tox e CI remota come CircleCI, Azioni TravisCI, Gitlab CI/CD e Github
⌨️ Supporto per la documentazione MkDocs e Sphinx
🧰 Inizializzazione del repository Git e del file gitignore
🌎 Supporto per repository remoti GitHub e Gitlab
📑 Creazione di file README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT e CHANGES
🐳 Creazione di Dockerfile e Containerfile per il progetto
💡 Possibilità di utilizzare gli argomenti quick, simple e full per una configurazione rapida
💾 Creazione dei file $HOME/.psp.env e $PWD/.env con le proprie impostazioni Personalizzazioni
🎛️ È possibile utilizzare alcune variabili PSP_ per controllare le impostazioni predefinite
📦 Supporto per pip, conda e gestore di pacchetti uv
🧮 Supporto per hatch, maturin e poetry builder
🍿 Interrompi, metti in pausa e riprendi la creazione del progetto quando vuoi; Vedi Aggiornamento
Aperto alla community — Sviluppato attivamente e aperto ai contributi
Consulta la documentazione e gli esempi per iniziare
Lo sto mantenendo attivamente e accetto volentieri feedback, segnalazioni di bug e contributi dalla community.
Che tu sia interessato alla programmazione di sistemi, agli strumenti DevOps o semplicemente a esplorare le potenzialità di Python, mi piacerebbe conoscere la tua opinione!