This is the third article in the Pyrseia series. The others are:
* Building Pyrseia I: The Idea
[https://threeofwands.com/building-an-rpc-library-i-the-idea/]
* Building Pyrseia II: Fleshing out Clients and Servers
[https://threeofwands.com/building-pyrseia-ii-fleshing-out-clients-and-servers/
This is the second article in the Pyrseia series. The others are:
* Building Pyrseia I: The Idea
[https://threeofwands.com/building-an-rpc-library-i-the-idea/]
* Building Pyrseia III: Server Middleware, Client Senders, CLI and InApp
Validators
[https:
Over at Highrise [http://https://www.joinhighrise.com/], we're looking to
replace our internal Python RPC library. The in-house solution we're using now
isn't particularly bad, but
This is the third post in my series on the inner workings of attrs. Here are the
others:
* attrs I: The Basics [https://threeofwands.com/attrs-i-the-basics/]
* attrs II: Slots [https://threeofwands.com/attrs-ii-slots/
This is the second post in my series on the inner workings of attrs. The series
starts here [https://threeofwands.com/attrs-i-the-basics/].
Out of the box, attrs can customize your classes in two