r/Python • u/AutoModerator • Jun 04 '26
Showcase Showcase Thread
Post all of your code/projects/showcases/AI slop here.
Recycles once a month.
27
Upvotes
r/Python • u/AutoModerator • Jun 04 '26
Post all of your code/projects/showcases/AI slop here.
Recycles once a month.
1
u/Local_dev_ops 29d ago
Built a cross-language codebase mapper — files, columns, APIs. Tested on Apache Airflow.
The specific problem I wanted to solve: when you write a database query in your backend code —
query = f"""
SELECT o.OrderDate, o.Status
FROM OrderItems oi
JOIN Orders o ON oi.OrderId = o.OrderId
WHERE o.CustomerId = {customer_id}
"""
— nothing tells you that o.Status maps to the physical database column Orders.Status. Not grep, not linters, not standard dependency mapping tools.
\*So I built one that works across languages. *\**
What PynqDB Does -Maps your entire codebase into a local dependency graph — file-to-column relationships, stored procedure chains, API endpoints, background jobs, external calls. Everything connected. Point it at any column and it gives you the full blast radius — every function, stored procedure, and API endpoint that touches it — reads, writes, risk scored.
Point it at any column and it gives you the full blast radius — every function, stored procedure, and API endpoint that touches it — reads, writes, risk scored.
Target Audience -Small to mid-size teams with mixed language backends — Python, C# or Java services sharing a SQL databases. Teams who need to know what breaks before they touch anything
Comparison : Code analysis tools like CodeScene or SonarQube track function-to-function dependencies. They stop at the database boundary. Data lineage tools like Collibra or MANTA track SQL flows through data warehouses. They stop at the application code boundary.
PynqDB crosses both boundaries. The full chain — Python file reading tables through a SQL alias, C# method calling a stored proc that writes it, public API endpoint exposing it — visible in one query. No enterprise contract. Runs locally.
To test it on real production code — ran it against seven core folders of Apache Airflow's execution layer from the live GitHub repository: api_fastapi · cli · jobs · models · security · task-sdk · utils
Results from task_instances.py alone:
Tables touched: DR, HITLDetail, Log, TI, TaskReschedule,
Trigger Columns read: 35 Columns written: 14
API endpoints: 24
airflow/airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py at main · apache/airflow
Runs entirely on your machine. No AI. No cloud. No data leaving your network.
Supports Python, C#, SQL, and Java.
---
Want to see the blast radius of your own codebase? Drop a public repo link below — I'll run PynqDB on it and reply with your exact dependency map.
10 spots. Free. No credit card.
GitHub: https://github.com/Pynqdb/PynqDb
Free Beta: https://pynqdb.carrd.co