> normal syntax. Right. Ok we have a problem with definitions. No this is obviously not normal syntax. Unless we take it to mean "whatever new syntax python i

> normal syntax. Right. Ok we have a problem with definitions. No this is obviously not normal syntax. Unless we take it to mean "whatever new syntax python introduces is normal syntax, since it supports it!", which is tautological and not very useful. I'm gonna say something, strictly so you can understand where I'm coming from, not to offend you. You sound very young. And by "young", I mean so young to not remember that Python was always about "duck typing" and not about strict types. I still have books on my bookshelf that tried to dissuade you from using "issinstance(foo, sometype)". So no, it's not python or normal syntax. Yes, Python now is safer than older Python. But I had 99 problems with Python and that wasn't one of them :( You, speaking as if Python is progressing so fast while Go is standing still, feels disingenuous. Go fixed their dep/packaging woes in a few years, Python is not even close. Go is adding generics. Go becomes faster in almost every release. Changing Python into something that doesn't resemble python, its values, or the reasons that people chose it in the first place doesn't make sense, nor does it make it "Python". I don't want Python to become Haskell, Rust or Go. No one ever chose python for its typing system! Rather its lack of it. Anyway, there's no accounting for taste and to each their own. Cheers