Way to confirm stereotypes that programmers are abrasive and narrow minded. Writing code may be a good way to learn programming; that doesn't mean it's ideal for discussing economics. For one thing, even for an expert the code takes longer to read than a baldly stated list of assumptions. And not everyone is a Python expert.
> if I’m wrong, either Python is computing the wrong answer, I got really unlucky [...] or one of my assumptions is wrong.
Umm no. This is a false alternative. How about a lot of assumptions being left out altogether. E.g. it's pretty clearly assumed that this doesn't affect economic growth, any benefits resulting from changed income inequality [1] are left out, inflationary effects do not exist etc. Any half serious student of economic modeling would have a field day picking out all the details routinely discussed in macroeconomics that this analysis is ignorant of.
And anyway who are these financial results even calculated for? If it's the government, then the expenses are fully incurred, but the "JK Rowling factor" is taxed at less than 100% to compensate. If it's the average person, you need to somehow factor in the benefit of reading Harry Potter!