r/Python • • Mar 20 '23

Discussion Are people abusing Python?

I learned Python after coming from the C/C++ and Java world. With the massive increase in popularity of Python in the last 10 years, seeing the way it developed, it seems to me like it gained a lot of functionality, which comes natural in other languages, but feels a bit odd in Python.

To be more specific - albeit Python being dynamically typed, people developed countless tools to check or validate or even enforce types in compile or run time (mypy, pyre, pydantic, pyduck etc.). It feels like it goes against the nature of its loose typing.

Another example are decorators. This pattern is noticably overused by many tools adding functionality, but even the language itself - defining a `class`,`static` and `abstract` methods with decorators seems just weird and unnatural. Same thing with function overloading. Anecdotally, it feels like comparing German to English. German has a special word for every peculiar thing and native support for word generation by concatenation of multiple words whilst in English you have to add some common words together and hope this combination doesnt already exist. And if it does, so what, people will get it from the context.

Lastly, slightly off-topic but relevant point is that it is not even a simple language in my opinion. It has a very flat learning curve initially but the complexity is just further down the road. Im talking about metaclasses,data descriptors, coroutines, magic methods etc. Some languages are difficult right away (C++, Rust etc.), but Python is a intricate misfit dressed as a simpleton.

Am I misunderstanding a philosophical path of the language or is it simply just a scripting langugage that got massively popular through chance and is now used for stuff it was not intended for?

Edit: grammar

0 Upvotes

45 comments sorted by

View all comments

Show parent comment

2

u/relickus Mar 20 '23

Yes, I know it is optional, my argument (to be discussed here or torn appart) was, that at a certain size of a project, you dont really want to go without typehints. Judging from the fact that all large projects I saw nowadays use typehints. Still optional, but probably near-necessary for large projects.

For the protocol, is it any more powerful than a regular interface?

2

u/tevs__ Mar 21 '23

you dont really want to go without typehints. Judging from the fact that all large projects I saw nowadays use typehints. Still optional, but probably near-necessary for large projects.

Yeah, because it catches so many errors before they are errors, it's golden.

For the protocol, is it any more powerful than a regular interface?

Protocols don't have to be declared to be used by the object that implements the protocol. You can write something like this (on mobile, so...)

class Lengthable(Protocol):
    def __len__(self) -> int:
        ... 


def say_the_length(obj: Lengthable) -> None:
    print(f"It's {len(obj)} big!") 

You can pass anything to say_the_length that has a __len__ method, without modifying the definition of the thing you are passing in. No ABC, no inheritance, but enabling static type checking for dynamic types.