> I would like to know what issues you had with it, Specifically, I wanted "logging" from python; leveled logging handlers, with colors (like colorama) and per

> I would like to know what issues you had with it, Specifically, I wanted "logging" from python; leveled logging handlers, with colors (like colorama) and per-module level permissions. > as I'm in the middle of building out my own replacement logging package None of the alternatives did exactly what was needed. And this extended other modules as well. It turned out we would be maintaining forks of all these projects. If you haven't already, https://github.com/avelino/awesome-go#logging https://github.com/avelino/awesome-go#logging is a good resource. If the original poster / you do decide to go with golang I wish you the best. It's a great programming language - but you're time spent reinventing the wheel will outweigh golangs benefits over python. And it's kind of a shame. The benefits of the static type checking, concurrency, compile times, testing, etc. I can tell you, in every category - at the present moment - golang's available libraries fall short to what you get in python. Not golangs fault, it's just want maturity gives you. Even things like asserts in python, (assert is even a builtin in python, no need to import unittest!) is non-existant in golang. It's not a "bad" thing. My outlook for golang it strong - my concern is that you may drain away your runway doing what you should otherwise be doing on freetime.