I've been dealing with some tax-related data and calculations lately and once again, thinking about how best to add jupiter notebook-like functionality to my editor.

My editor is written in Python (by me, in fact) and is easily extended with new commands written in the language. I have a "pyx" command that executes the selection as python code, so it's really just a matter of providing some functions to let you perform operations on the current buffer, itself which I've started doing.

I'm happy to announce that I have retired from tech. Today was my last day on the job.

I had an extremely good run. Caught the wave in the early 90s and rode it clear onto the beach of AI. One way or another, I don't think the industry will ever be the same again and I'm ready to move on.

Looking forward to spending the rest of my years focused on music, my own software projects, my kids and outdoor activities. Currently kickin' back with a cold one. 🙂

For years now I've been trying to figure out the best way to deal with the string/bytes dichotomy introduced in python 3. I think I've finally got it.

The "surrogateescape" error handling mode will translate invalid utf8 byte sequences into a special range of the utf8 character space intended for just that purpose. For example:

>>> bytes(str(b'test \0 with \xa0', 'utf8', 'surrogateescape'), 'utf8', 'surrogateescape')
b'test \x00 with \xa0'

Would have been nice if this were the default.