Have to add that we work exclusively in strongly-typed languages. Kinda want to see how it plays out, but I can't help but argue with him, so I think I'll just go.

you are viewing a single comment's thread
view the rest of the comments

[–] Pyro 24 points 3 days ago* (last edited 3 days ago) (2 children)

Python 3.x will never have static typing because that would break backwards compatibility.

However, typing hints have been Integrated into Python for a while, and you are heavily recommended to use them, so your IDE can enforce typing.

[–] [email protected] 2 points 1 day ago

Also have the option of selectively/strictly enforcing in CI, to get an experience & protections similar to "compile-time type checking"

[–] [email protected] 3 points 3 days ago (2 children)

Considering there is typing in the code why is there no switch to enable type checking at runtime? PHP does this with a per file declare(strict_types) - why would python be unable to have either a global or per file flag to enable checks?

[–] [email protected] 2 points 1 day ago* (last edited 1 day ago)

why is there no switch to enable type checking at runtime?

Have you got problems this would solve? I've done a lot of type annotated Python at scale and I can't think of an example.

Edit: given nobody in their right mind allows code that's not checker clean.

[–] Pyro 10 points 3 days ago (1 children)

Typing when you need it gives you more freedom over a toggle. You can choose to type some parts of the code while leaving other parts untyped.

For example, if I'm writing a quick and simple Python script I may forgo typing, but when iterating on it I'd go back and add the types I need.

[–] [email protected] 4 points 3 days ago

This isn't an issue, though. PHP has the same partial typing flexibility. There are ways to solve that issue and even typed PHP still allows union types including mixed which allows any types.