Pyblosxom 1.5.3 — the engine powering this blog — was last released in 2013 and officially targets Python 2.7. It does include a use_2to3 = True flag in its setup.py, which historically instructed setuptools to auto-convert the source at install time. That mechanism was removed from setuptools 58.0 (2021), so the package now installs as raw Python 2 code on modern systems.

The upgrade path to Python 3.12 required two layers of fixes:

Automated conversion via 2to3

The Dockerfile runs 2to3 -w -n over the installed Pyblosxom package directory at build time. This handles the bulk of the syntax differences (print statements, has_key(), except E, e style, etc.).

Manual patches for removed APIs

2to3 converts syntax but does not know about API removals. A startup script (patch_pyblosxom.py) applies targeted fixes each time the container starts, covering:

• __init__.py: implicit relative import from _version import → from ._version import
• crashhandling.py: cgi.escape removed in 3.8 → html.escape; StringIO.len attribute gone → len(output.getvalue())
• pyblosxom.py: entrylist.sort() on objects that only define __cmp__ (ignored in Python 3) → explicit key= lambda
• cache/base.py: 2to3 converted self.has_key(key) calls to key in self, which recurses infinitely because the class has no __contains__. Fixed by patching __getitem__ to call isCached() directly and adding a proper __contains__ method.
• plugins/markdown_parser.py: story.decode("utf-8").encode("utf-8") round-trip is meaningless on Python 3 strings → pass story directly.
• renderers/blosxom.py: "".join(content) fails when a stray bytes value slips through → decode any bytes items before joining.

The local plugins (bib.py, pycalendar.py, pyarchives.py, etc.) also needed porting: print statements, dict.has_key(), mixed tab/space indentation, and the _bibtex C extension (Python 2 only) was replaced with the pure-Python bibtexparser package.

What's the point of this you might be asking? Experimenting with AI and what it is capable of. Most of this tedious back and forth work was done by Claude. It's a pretty powerful paradigm if you can point it to the output and iterate semi-autonomously.

Mailsink got a makeover as well.

Planning to move this to Hugo eventually, but for now this has to do.

posted at 14:00 | path: /python | permanent link to this entry

After roughly 2 years I found some time again to touch this blog. I have to move hosting providers and thus I'm migrating everything to Docker containers. While working on that I noticed that half of this blog isn't working, upgraded to Pyblosxom 1.5.3 (deprecated), and hopefully fixed most of the broken stuff. Maybe I even get to write more. In the meantime at least the obvious stuff is fixed and working. Enjoy!

posted at 01:42 | path: /web | permanent link to this entry

I'm maintaining this soccer stats sheet and have different games on different sheets. To build up sums I like to reference data from the previous sheet. It took me some trial and error to get going. Essentially it requires a custom function and the use of INDIRECT.

For the custom function go to Tools > Script Editor and paste the following code

/**
 * Retrieves a reference to the previous sheet, or null
 * input is unused.
 */
function prevSheet(input) {
  var sheet = SpreadsheetApp.getActiveSpreadsheet();
  var sheets = sheet.getSheets();
  var prev = null;
  for(var i = 0; i < sheets.length; i++) {
    if (sheets[i].getSheetId() == sheet.getSheetId()) {
      return prev.getName();
    }
    prev = sheets[i];
  }
  return null;
};

The code is also available here as an add-on.

To use the function you need to use the INDIRECT function, for example to reference cell A2 on the previous sheet:

=INDIRECT("'" & prevSheet(GoogleClock()) & "'!A2")

To be able to copy the formula around and keeping the references, use

=INDIRECT("'" & prevSheet(GoogleClock()) & "'!" & CHAR(64+COLUMN()) & ROW()

This was very helpful to get me started.

posted at 09:23 | path: /web | permanent link to this entry