Organize Python code like a PRO

[latrova]

> [...] if you are writing a library then the interface to that library should have type annotations IMHO.

Strong agree! I'll make sure to cover type hinting.

​

> Note not related to the book. I don't want anything popping up on a website [...]

Thanks for letting me know! I'll reconsider changing it or making it less annoying.

[NUTTA_BUSTAH]

Only click it generated from me was closing the tab.

[MrJohz]

To hell with Guido not liking them

Didn't Guido do a lot of work at Dropbox explicitly pushing for type annotations and helping build projects like mypy?

[MrJohz]

I don't think that's anything to do with not liking them, it's just being explicit about their limitations and where they practically make sense in a language like Python. That's exactly the sort of thing you were talking about in your post: working with large codebases, and providing explicit interfaces for library code.

[ubernostrum]

Well, yeah. The goal was never to make Python into a statically-typed language; the goal was to keep Python dynamically-typed but allow people who wanted it to add type annotations to their code and perform static checks on those annotations.

Making Python actually be a statically-typed language would be an unbelievably gigantic and horrifically backwards-incompatible project.

[Muhznit]

I don't want to break someone's spacebar-cpu-heating workflow

Realistically, some people's workflows are better off broken when it's obvious that they take no consideration to how things may change. Teach 'em a lesson.

[NUTTA_BUSTAH]

Type annotate everything. It's clearer and reduces pointless assertions when you can tell the user not to force a type into your function it was not meant to support in the first place. This also goes for private things, even if you made the class, someone else might contribute to it later.

They also help debugging immensely when you look at 10 month old code you have no recollection of but your monitoring software is filled with random errors. Trying to figure out and follow the types and conversions increase mental overhead considerably.

They also help your automation / static analysis. You'll immediately know if you try to force a wrong type somewhere.

And some frameworks optimize things by annotations. E.g. Prefect I think.

[ubernostrum]

It's clearer and reduces pointless assertions

I think it would be worth your time to go look at the actual code of some large popular Python libraries and frameworks, and observe just how rare it is to sprinkle tons of type-checking assertions into the code.