math2001 / nine43 Goto Github PK

I originally implemented net.JSONStream.aclose by just closing the underlying stream because I had forgotten about send_eof, but now I'm not sure what are the benefits of it.

What do I gain by being polite? Less angry error messages? Letting the other one know that we're willingly closing, and not crashing? Could that result in a different behavior from the server? Should net.JSONStream raise a different error?

There's this very interesting package called Eliot, that propose a different approach to logging.

For sure, the current way logging works is just very inefficient. Firstly, debug isn't always enabled (and leaving every module's logging level to DEBUG would be a nightmare), and even if it was, it's so painful to look through it, and track on particular thing (concurrency doesn't make things any better).

From what I understand right now, Eliot does it using actions. A program is just a collection of actions, and Eliot monitors them, and record how they behaved. It's seems nicer for debugging and monitoring perfs.

1. dump surfaces to files, and then compare them.
2. check states changes as we trigger events in a sandbox (can we do that with pygame? If not, then that means that I'll have to build some annoying abstraction).