tree d3e89acb9741ab9b5a2f90c12fd40e2fbe7a5763
parent b1c3a90fb12ff6ce15f06f7e80ee5eafbb88665c
author Sam Clegg <sbc@chromium.org> 1790982865 -0700
committer GitHub <noreply@github.com> 1790982865 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJqwDrRCRC1aQ7uu5UhlAAAmKgQABWMXL7yQlAbfjG7qmDIniwt
 9B+h6j0MxpBZIFoXT1Sa39IXZM/ScTZySjlL+yXpx+kQc4LdL2fJ5SKSlP8O77FU
 BXryl+AEcc5f/A2DycbZA2bzZMCtmwFqjue3B+OdyyAV2CF88HBMv/miRvmaGWqo
 PunSrtxt18p6NJ4FIYiqZm4I5CH6+Z1U6Qfb+ZRFmO2NG+XsUkkXzuzCg0OmA/yX
 s0u+/O/ou6ytLI/8rXdfro8CcW8ENwddKLw97VpAwUfKEkg0QwL9EesvZazKlqhZ
 tihXwsmaJUUKFxoU6P7KYXi3RPSjYo7W8FDRevaIMCKPdwZREdI+p2jvAIPHY/F4
 ziGJfkEpeo/JrANsD950Sq+Mq/pulLoBtz4t0MhHof0CFunFCXdoJqSExQDuzzAU
 drPpFOKqKi4W/62+Owwff4ulRRqquKeSGgAiS5fJSokzqlEs9IzYmT68Y+hY2hrj
 QmD442w/85a3ITO5/d9hzB9VWZpiJZ+ILlTUtAe1OrTMRO7iTrTIkWrJRGTVQcXk
 3gAEk+1xenSISlQAErLNRCBvqiwQ8G+uJ+V+kX/oxQwbZYNrIhZJtragCDxcBTym
 J4LxnqloCTIwTs0VOfnGIYtx7RjIM6YXbYz2yjmo47sFhckhKBx+bd83cvMHQhFd
 pMpvPvwFy+Ey/lq+jbGW
 =mAVc
 -----END PGP SIGNATURE-----
 

Re-indent python using 4-space indentation. NFC (#1799)

This change was generated using:

```
$ pip3 install reindent
$ git ls-files '*.py' | xargs reindent -n
```

Why is this good idea? Mostly for consistency with the rest of the
python world. Other projects in our ecosystem already use 4-space
indentation:

- binaryen: Converted to 4-space a while back
- llvm-project: Has always used 4-space IIUC
- emscripten-releases: Converted to 4-space a while back
- wabt: Has always used 4-space
- chromium: Start converted to 4-space several years back.

This is also kind a trial run for doing the same thing in emscripten.
Hopefully it won't make rebasing outstanding branches too painful (AI
agents are really good a re-basing these days anyway). I confirmed that
an agent was able to immediately rebase each of my outstanding 18
changes on top of this change despite them all (obviously) have
conflicts.