Brandt Bucher

CC @vstinner

This is mostly done! All that's left is compressing `lnotab`, and being smarter about our stack size calculations.

Don't bother with any PR's right now, I think this project will get a pretty heavy refactoring in the near future. `_PyTuple_Resize` is probably not coming anytime soon, for technical...

> The trick is to use `byref()`. Ah, nice. Part of the reason I created this library was because I found `ctypes` such a pain to use. Glad it can...

I feel like this is already getting a bit off-topic. 🙂 > I think it would be valuable for maintainers (e.g. me) and users to better understand why things are...

> I understand that you can't cover every decision, but an overview which documents some of the key decisions would be very valuable, IMO. Well, that's what PEP 635 is...

> curious question: would the parser be able to distinguish `float(42.0)` and `42.0`? Then if someone wanted to be really pedantic about their floats and ints one might be able...

> ... also now that we know how to distinguish (`bool`), `int` and `float`... how does one spell just any old number; `case Number(x): ...` with `Number` from `numbers` doesn't...

Agreed. I guess the only remaining question here is: > If we were to change the semantics of `case True`, would that mean we'd also change the semantics of `case...

Well, in terms of implementation it would probably just be a new opcode that does the correct comparison at runtime, rather than separate compile-time code paths. But your rationale for...