Better apply for a mutable library card now before someone else does

In, out, and ???

I’m gonna have to borrow this book

I think what you have is the perfect amount of complexity, and easily extendable. I use callbacks like this all the time in my code, but also my users are part of my team at work so they don’t have far for help when the callback API isnt clear :P most of my users dont even know callbacks are a thing.

If your list of supported events gets large or you want to cheaply support future changes to the server, you could pass all event names and data through a handler callback and make users handle multiple event types.

One of the things that makes plain callbacks nice is it’s an easy way to let your users decide how they want to integrate with your library. If your callbacks are called from a background thread, it’s up to the user to figure out how they want to pass the event to other threads. Async users can use their runtime of choice to submit tasks from a callback.

Kind of silly since python is basically source code in wheel form, but you have the package on pypi listed as gpl3 but don’t provide a source repo link.

Also, I write worse code than this and get paid a lot for it :P don’t sell yourself short

I would import whatever functions you want users to use often in the init script of the ogsapi module … But idk python packages are all over the place with stuff like that, it’s definitely not required.

The most dangerous curl sudo bash on the internet :P meh it’s probably fine…