Péter István Fülöp’s Post

I was able to craft a snap for a Python app called pyfiglet. I was able to follow along using this tutorial -> https://lnkd.in/gJuQjFB2 This involved installing Snapcraft and LXD, defining the package information, troubleshooting target platform. Seeing the result was a great feeling!

I am planning to develop weekly projects that can help people anyway. The source codes will be publicly available on Github. The projects will be based on Python along with other technologies. That would be fun, won't it?

Claude Agent SDK tracing in LangSmith just got an upgrade. Now you can trace: → Subagents → Child runs inside MCP tools → Cost tracking + more Update to the latest Python SDK to try it out. Docs: https://lnkd.in/gTaNkWMa

I’m excited to share my latest Python project – a simple Expense Tracker built using core Python fundamentals. This project focuses on strengthening the basics and demonstrates how powerful simple concepts can be when applied effectively. It is developed using: • Variables • Lists & Tuples • Functions • Loops (for, while) • Conditionals (if-elif-else) • User Input • Basic Data Handling To make it beginner-friendly, I’ve also included text files with line-by-line explanations of the code, so anyone starting with Python can easily follow along and understand the logic behind the program. You can explore the complete project here: https://lnkd.in/gdce9UUX This is a great hands-on project for beginners looking to build a strong foundation in Python and understand how to structure small real-world applications. I’d appreciate your feedback and suggestions! #Python #BeginnerProject #PythonProjects #Coding #LearnPython #Programming #SoftwareDevelopment #100DaysOfCode #TechSkills #CareerGrowth

VSCode workspace is a game changer! If you're writing Python codes for different versions (2.* and 3.*), then you should try the workspace in VSCode. Basically with workspace, you can define/set which CPython version to use when you click the play/run button in VSCode. This is very useful in cases where you might be trying out a logic in Python 2 and also on Python 3, or when you're migrating either upwards (from 2 to 3) or downwards (from 3 to 2), and since it's on the same IDE, the experience is really enjoyable. This also works on the same major version, so maybe you have Python 2.2 and 2.7, or 3.10 and 3.13; and it's not limited to just 2, you can have more. First time I tried it, had me smiling :) cause I work on different versions and it's not fun going to console and manually typing which python version to run on which folder --- (side note: python launcher is a great tool, but having an IDE that can support multiple versions seamlessly is just another level of ease). I really liked it, try it and see for yourself ;) #vscode #workspace #dcm #python

For those that have errors in their #python code ;-) here a way to customize the output with colors and other stylistic elements: PrettyErrors https://lnkd.in/eK-4_-mM

Turning an n8n workflow into a Python script and running it on GitHub for free is easier than you might think. Here’s a simple way to do it, especially if you want to run scheduled workflows. First, download your n8n workflow as a JSON file. Next, upload that file to Claude and ask it to convert the workflow into a Python script. Once you have the script, create a new GitHub repository and add the Python file. Move any API keys or sensitive information into GitHub Secrets to keep them secure. Then, ask Claude to guide you through setting up a GitHub Actions workflow that will run your script on a schedule. That’s it. Now your workflow runs for free on GitHub, without needing to keep n8n running.

Built a simple File Reader CLI in Python today. This project takes a file path as input, opens the file, reads its contents, and prints everything directly in the terminal. What I learned while building it: • Taking user input with input() • Opening files using open() • Reading file content with read() • Using with for safe file handling • Adding error handling with try/except Small projects like this are helping me strengthen my Python fundamentals and get more comfortable with writing clean, practical code. GitHub Repository: https://lnkd.in/gud495tr #Python #PythonProjects #CLI #CodingJourney #Programming #LearningInPublic

I’ve been using Jupyter notebooks for years, but they tend to get messy once they stop being "temporary". I recently tried marimo, and it feels like a different approach: • notebooks as plain Python files • dependency-based execution (no more weird states) • much cleaner to keep in git What I like most is that it sits somewhere between a notebook and a small app. I also show a real example: using it to recover deleted S3 files. 👉 https://lnkd.in/d_YdRCbd

I hid an Easter Egg in our tooling… It’s fast. In case you haven't heard, there is a new kid on the block doing fast type checking: ty https://docs.astral.sh/ty/ ty is a new type checker from the team behind ruff (the linter that already replaced flake8 and black for us). It's written in Rust. Same idea: take a critical Python dev tool and make it instant. Our Python codebase runs mypy on every commit and every PR. It works, but sometimes you see that 2-3 seconds wait that even on a mid-size project, it adds noticeable seconds to every pre-commit hook and CI run. Multiply that by every developer, every push, every day. What we did: 1. Tested removing the Pydantic mypy plugin, zero new errors. It wasn't catching anything our type annotations didn't already cover. 2. Ran ty alongside mypy to compare output. 99 initial errors, all from third-party library stub gaps (SQLAlchemy, pyarrow), not real bugs. 3. Added per-module overrides in pyproject.toml to suppress the stub noise, same thing we were doing with mypy's # type: ignore comments. 4. Swapped mypy for ty in pre-commit, CI, and our justfile. Removed mypy entirely. Result: Type checking went from "look out the window" to "already done." Same coverage, same confidence, faster feedback loop. Should you migrate today? If you rely heavily on mypy plugins (Pydantic), test without them first. If your codebase passes clean, you're good to go. If not, wait for ty's plugin ecosystem to mature. You could argue that ty is still early but is moving incredibly fast. For well-typed codebases, it's already a drop-in improvement. Migration inspired by https://lnkd.in/eu5iMfS2