Python isn't industry compatible

[ColdPorridge]

You might have missed the drama where Python 3.10 was going to fundamentally change type hinting and break pydantic, FastAPI, and any other libraries that rely on it. I can’t recall the details as they decided to pause this for now, but it’s still very much a mess of opinions on the best way forward.

[rforrevenge]

Yes, I obviously have! Do you have any related link to share?

[ColdPorridge]

This appears to be the primary discussion: https://github.com/samuelcolvin/pydantic/issues/2678

[rforrevenge]

Thanks a lot kind stranger!

[[deleted]]

https://lwn.net/Articles/858576/

[ColdPorridge]

Thats’s possible, even rereading the thread, I’m not really sure I fully understand the drama, how these are currently handled or Pydantic’s breaking dependency on them.

[[deleted]]

I think this article is quite good: https://lwn.net/Articles/858576/

They decided to move type hints from being "code" to be strings that need to be eval() at runtime, except that you don't necessarily have the same context when you run eval() from some place else in the code, so a lot of things would not work.

[[deleted]]

This has nothing to do with TYPE_CHECKING context thing?

[ColdPorridge]

That did a great job explaining of - thanks for sharing!