For a while now, I’ve been wondering how to combine entr
(which automatically runs commands on file changes)
with the way I setup project validation (both for CI/CD and for local developer usage) with Makefiles.
The best thing I got so far is the
validate_continously target in
I finally integrated isort into my toolbox.
I think that the job of changing code files belongs to the editor (or an IDE),
so I made Vim run
while the import order enforcement in a project is done via Makefile
(which can be run the same way by developers and the CI/CD pipeline).
I’ve created a script that should 1 set up a fresh Manjaro with all the software and configuration that I want in a workstation. It can also update the setup on being rerun. Now I have two laptops that behave and look the same 2, and it’s easy for me to maintain that state. Oh I wanted that for a long time :)
Finally doing some scripting today. I noticed that there are some python-virtualenv-related commands I run often (in my tmux-based “IDE”), so I automated them away to shave off some keystrokes.
A useful feature many web frameworks have is auto-reload. Your app is running in the background, you change the code, and the app is restarted with those changes, so you can try them out immediately. What if you wanted that behavior for everything that you’re writing? And without any coding to implement it over and over in every little project?
Replacing its own definition is a fun/horrifying thing that a Python function can do:
This year at EuroPython (and not only there), I gave a talk about Test Driven Development of Python microservices. I guess you can check it out, if you’re into that kind of stuff. It’s also available in Polish.
I got tired of having to manually build and upload my library (Mountepy) to PyPI, so I decided to do what any sane programmer would do - set up automation 1. But how would my scripts know whether they need to just update the README on PyPI and when to assemble and push a new version of the library? Thanks to the AngularJS commit convention! Oh, and Snap CI will run the whole thing. Why Snap, you ask? See my previous article - Choosing a CI service for your open-source project.
I host my code on GitHub, as probably many or you do 1. The easiest way to have it automatically tested in a clean environment (what everyone should do) is, of course, to use one of the hosted CI services integrated with GitHub.