Hacker News: tstordyallison

New comment by tstordyallison in "An oral history of Bank Python"

tstordyallison — Fri, 05 Nov 2021 00:05:25 +0000

I was waiting to see when someone would link to this :)

New comment by tstordyallison in "An oral history of Bank Python"

tstordyallison — Fri, 05 Nov 2021 00:04:23 +0000

Indeed.

Thankfully, I think it can be said the light is now strongly visible at the end of the tunnel on Python 3 (but it’s not completely done).

New comment by tstordyallison in "An oral history of Bank Python"

tstordyallison — Fri, 05 Nov 2021 00:00:58 +0000

I find it amusing that Bob made it in most of the banks, but few of the other names stuck.

New comment by tstordyallison in "An oral history of Bank Python"

tstordyallison — Thu, 04 Nov 2021 23:57:34 +0000

It’s not just straight pickle (usually) - there’s a layer in between that allows at the very least for the handling of deprecated fields/new fields/renames etc.

But - after a change - you have to choose either to leave that ‘backward compatibility’ in-place (essentially forever), or put together a job to run (on that scheduler! Hah) to go re-write in your new format. If you care enough, you might - and then you can remove your logic to handle the old names/shapes.

The charm in a lot of it is in its simplicity. It doesn’t claim to very smart, but people get it - and are often remarkably productive.

New comment by tstordyallison in "An oral history of Bank Python"

tstordyallison — Thu, 04 Nov 2021 23:48:29 +0000

One of the systems downstream of the JPM ‘Minerva’ (Athena) was called ISIS.

It was renamed…