4 ms·
This is pretty exaggerated. I've been in coding in Python for more than 10 years and I only rarely encounter code that suffers from the issues this article comp
by pdabbadabba 10y ago
This is pretty exaggerated. I've been in coding in Python for more than 10 years and I only rarely encounter code that suffers from the issues this article complains about, including Python 2 and 3. And the reason, of course, is that this article focuses on complex cases like chained asynchronous functions and optional type decoration but criticizes them as though they were representative of typical Python code.
Yes, if you want to write a system of asynchronous functions with type decorations, then yes it can get a little messy. But this isn't Python becoming less "austere and easy to read" over time, this is just identifying a case where Python is less readable than one might like.
I'm not sure what to tell you if you were looking to write asynchronous code without some amount of syntactic cruft. There are languages that can do this with a prettier syntax and less boilerplate (Go, maybe). But I don't think has ever included any version of Python.
- lima 10y agoNot to mention that it'd be even more messy if you were to add type annotations and async in Python 2.