---
title: "Python limitations in the agent era"
date: 2026-01-24
canonical: https://solmaz.io/x/2015170626399416660/
x_url: https://x.com/onusoz/status/2015170626399416660
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
---

I'm really starting to dislike Python in the age of agents. What was before an advantage is now a hindrance

I finally achieved full ty coverage in @TextCortex monorepo. I have made it extra strict by turning warnings into errors. But lo and behold, simple pydantic config like use_enum_values=True can render static typechecking meaningless. okay, let's never use that then...

and also field_validator() args must always use the correct type or stuff breaks as well. and you should be careful whether mode="before" or "after". so now you have to write your custom lint rules, because of course why should ty have to match field_validator()s to their fields?

pydantic is so much better than everything that came before it, but it's still duct tape and a weak attempt at trying to redeem that which is very hard to redeem

you feel the difference when you use something like typescript. there must be a better way. python's only advantage was being good at prototyping, and now that's gone in the age of agents. now we are left with a slow, unsafe language, operating what is soon to be legacy infrastructure