Try building a production rest api using flask, with encryption, authentication and authorization backed in, taking care of internationalization and localization. See for yourself how many lines of code you will need and obviously see which one is more readable and cleaner. Do the same with go and you will know what I'm talking about.
Go is good for its own use case for solving Google scale problems which requires additional efforts and time. Python is very approachable from the beginning. Moreover the wealth of documentation and help makes it so much easier when you hit a roadblock. You will need twice the amount of time to do the same in go.
Is there any way you can elaborate on your experience that brought you to this conclusion?
I am rather curious, as Go has the same middleware concept that django has to add in security, session, and token information to an http call.