Two months later than planned (as it usually goes with side projects ;), and a first release of Gimmecert, a small utility for issuing X.509 certificates for testing purposes, is finally out.
Should you ever work on a Python project to be consumed by the general public, sooner or later you will need to make it available on the Python Package Index (also known as PyPI). And, if you follow the Python Packaging Guide, you will learn about the tool to use for this purpose - Twine. Following the same thread, you might find out about the Test PyPI instance, which would seem like a perfect spot to try out your release on before making it available on the main PyPI repository. Except for one big gotcha...
Nudged by one of my remote friends (here's to you, Garen :), I realised that there hasn't been a single status update post ever since I moved from Serbia to Sweden. And, apparently at least some people like to know what's happening, so maybe it's time to step aside from technology stuff for a bit :)
Automation tools can help a lot reduce the workload. This does result in some magic happening behind the scenes. And when this magic fails, you need to dig in there, and try to understand what the heck is going on...
Or... What happens when you start thinking about packaging in Python world - package security.
Or... What happens when you start thinking about packaging in Python world - managing packages and dependencies.
Or... What happens when you start thinking about packaging in Python world - the poetic view.
Running your own CA for issuing client and server certificates is always fun. Unfortunately, it is not so fun when others visit your website and get a big fat red warning in their face.