The Phyton must be a superb language. A pity it doesn't exist.

When working with sets, it is more convenient to use operators instead of methods. even = { 2 , 4 , 6 } odd = { 1 , 3 , 5 } union = even | odd union ^ odd union >= odd union - odd odd & even

No big deal. Typically, key-value collections are unordered anyway. Muhammad Anas

Since Python 3.7 built-in dict is ordered. But saying that, one should not rely on it and use OrderedDict if such functionality is required. https://www.blog.pythonlibrary.org/2018/02/27/python-3-7-dictionaries-now-ordered/ https://www.geeksforgeeks.org/ordereddict-in-python/

Not exactly. Python is multi-paradigmatic. One can write Python program without using OOP if we do not count programming with objects. Compared to languages like Java or C#, no one forces programmers to insert the functionality into classes. The type inference is not exactly related to dynamic typing. On the contrary, types are inferred in statically typed languages to reduce the boilerplate and get closer to dynamically typed languages. The CPython interpreter doesn't infer types. Under the hood, he is examining objects in runtime. If the requested operation is not valid for an examined type, the interpreter raises an exception. Statically typed languages require types to be known before they enter runtime which is not the case with Python and dynamically typed languages in general. Python uses type inference for optional static typing, like in Mypy or similar. On the other hand, compared to languages like JavaScript, Python is strongly typed which is not the case with JavaScript. Finally, Python is a specification of a programming language, so it can be interpreted or compiled. CPython (the most common runtime) as its reference implementation has an interpreter while PyPy is compiled to bytecode if I am not mistaken.

I wonder why you didn't mention asynchronous programming with the async keyword. Right now, they are the preferred way when it comes to IO-bound operations. Anyway, the implantation of GIL is not defined by Python per se, it is just a well-known design feature of CPython. The other Python implementations are often GIL-free.

Fillers are usually a sign of sloppy writing, so no need to use them. But even technical articles may be accompanied with deeper insight, typically with discussion of pros or cons of the given approach. A longer article helps understand its reader not only what its author intended to convey, but even why he claimed that. Of course, if the author's intention is only to provide a quick tip, no wordiness is necessary. But on the other hand, such write-ups usually do not qualify for a full-fledged blog article. After all, some readers may end up disappointed that they got caught by too short note-like work, not exactly worthy of the click and wasted data. Moreover, it is said Google Search Engine tend to skip over too concise content, so the author gets disqualified from the global competition. Chris Bongers

1500-3000 words They say about 1k is enough to satisfy Google, but personally, I would recommend 1.5k as the bottom line. Actually, 1.5k words are the required daily minimum for writers of Chinese Online Novels if they want to get paid. I guess the Chinese companies (Webnovels and others) have their well-researched reasons to insist on this number. Over 3k words are simply too much. Modern readers need a break to relieve their shorter attention span.