steam.py VS python-betterproto

My library steam.py has some very basic support for workshop management (you can't currently create a workshop file) but it does have first class support for adding and removing children from a PublishedFile along with a rich representation of the file. The way PublishedFiles are handled is something I'm looking to improve so I'd be open to suggestions about the design or contributions

Depends on what language you're using for JavaScript I think the defacto is anything Doctor McKay makes https://github.com/DoctorMcKay/node-steam-user, https://github.com/DoctorMcKay/node-steam-user etc. If you use python, I'd recommend https://github.com/Gobot1234/steam.py (I'm totally not biased). If you use C# then SteamKit is always a good option. If you use rust then SteamHelper looks interesting although doesn't support too many trading bot features

For context: in a project I was working on recently, we relied heavily on Protocol buffers. All our internal and external services expose a GRPC interface. Also the client libraries that are used by the end users rely on the Proto service interfaces. However, shipping simply the generated code that comes with the official protoc Python plugin or any other standardised Python protoc plugin (like betterproto) was not sufficient for us. We wanted certain modifications and additions to the generated client code like service clients that would automatically pick up credentials/service account files, a more Pythonic handling for requests that work with pagination or long running operations etc.