Ehm, good question! When I started writing Pygrister, implementing sessions was in my todo list… then I totally forgot about that.
I’ll look into it at some point, but it’s kinda tricky. Integrating sessions in my code would not be difficult in itself… the problem is, you don’t want to always enforce sessions: users should be free to use them or not. So, I have to figure out a way to offer the choice, withouth breaking the exsistent api: maybe a switch like “grist.use_sessions = True”… but I’m not sure yet.
As always, writing code that more-or-less works is easy. The hard part to figure out is the interface for your code.