Software Development Leader
In 2013, I attempted to get in on the Crytpo game. I applied for an account at MtGox, which took months to be approved. In February, I wired a substantial sum of money to them the day before they were hacked. Luckily (or maybe unluckily), my bank was able to reverse the wire and recover the funds. Later, I bought into Bitcoin through Coinbase.
I was recently asked a few questions regarding documenting open source software:
I’ve recently made the transition from setup.cfg to pyproject.toml across the suite of projects I maintain. It was mostly automatable, thanks in large part to the ini2toml project.
Open source software (OSS) development is vibrant and exciting, with enterprise-grade continuous integration, source code management, and even some AI features like Copilot. Leveraging techniques like an SCM-managed skeleton and auto-enabling plugins has enabled some scalability, but leaves much to be desired. In particular:
GitHub Actions, probably the most popular continuous integration (CI) system for open source projects provides a facility for running a series of jobs across a matrix of factors such as operating system, language version, and more. This mechanism makes it easy for the user to quickly define the factors representing supported systems. For example:
Many of the projects I maintain in open source make heavy use of doctests. Supplying doctests affords a luxury and elegance not offered by unit tests, namely:
Twenty years ago, PEP 257 introduced docstrings. Yet, it’s still not obvious that docstrings are nice and preferable to comments.
I’ve hosted the jaraco.com email on Microsoft Exchange since 2000 when I ran my own Exchange server on a Comcast internet connection (before they capped upload speeds and blocked ports capriciously). Sometime around 2010, I moved my domain to “Microsoft Online” (hosted Exchange). And for a long time, this service was great.
Want to develop Python applications, but realize the dependence on the network and PyPI is a hindrance? devpi provides a robust way to keep a cache of all the packages you need to develop. And it’s super-easy.
Today, a strange thing happened. My partner and I returned from lunch when she resumed her Surface Studio running Windows 10 19042.985. Upon doing so, two Windows Defender alerts popped up, indicating that features were blocked for two processes, taskhostw and sihost, both in \Windows\System32.