Python 3 Types in the Wild

Re:Python 3 Types in the Wild by musingsole on Friday March 18, 2022 @01:11PM (#30724802)

> trust that the static types are truthful

That's often a mistake even in typed languages like typescript. Satisfying a static type analyzer isn't enough. Real data is whatever it is going to be. If your types are meaningless at runtime, you can easily encounter type mismatches.

Static typing as implemented in typescript and python type hints is a tool for engineers instead of a tool for systems.

[ Parent | on HN ]

Re:Python 3 Types in the Wild by roywiggins on Friday March 18, 2022 @01:21PM (#30724932)

The types are usually ignored, but not entirely erased- Pydantic uses type hints to do validation at runtime, so if you construct a Pydantic object with invalid data it will throw an error, so eg

    foo=PydanticFoo(**request.json())

Will try and validate a json request against the implied schema provided by the type hints on PydanticFoo while constructing it and will throw if it fails.

[ Parent | on HN ]

Re:Python 3 Types in the Wild by goodoldneon on Friday March 18, 2022 @02:03PM (#30725469)

You missed my point. If you validate input, then the static types are representative of runtime types

[ Parent | on HN ]

Re:Python 3 Types in the Wild by musingsole on Friday March 18, 2022 @03:11PM (#30726276)

Ack, so I did :P

[ Parent | on HN ]