This is not an easy case, even with the support of PyO3. This short article gives a nice blueprint to share a reference between Rust and Python.
Its use cases are indeed limited. It's a success for network IO. For everything else, the free threading might be the path forward once it stabilizes.
Looks like an interesting alternative to the bigger Django and FastAPI which get all the attention.
It's just hard to make Python fast. It can be improved yes, but it'll stay cache un-friendly without a redesign. Nobody wants a Python 4. :-)
uv really opens the door to nice features for Python. Now with a standardized PEP to help the configuration it's getting even better.
Early days but it looks like we got two interesting type checkers coming up for Python. Definitely worth keeping an eye on them.
Or why I'm still on the fence regarding async/await. It's rarely the panacea we pretend it to be.
Nice trick for numbers formatting as strings in Python.
Good proposals to shorten the time spent executing tests. Tighter feedback loops make everyone happy.
Good list of interesting features in Python. Some are tied to the gradual typing system but not all of them. Definitely tricks to keep in your bag.
A new type of strings to keep an eye on in the upcoming Python release.
There's a sustainability issue for the REST support with Django. Hopefully this will resolve.
Nice little Python trick using bidirectional generators.
More feedback about uv use in the wild. This is getting really close to becoming the de facto solution for new projects.
Looks like an interesting DSL to write high performance Python code.
Nice exploration of JIT based techniques in Python.
Looks like a nice resource to handle the coming move to free threaded Python.
Nice trick for cleaner interruptible python scripts indeed.
Nice comparison of both approaches. Some of the criteria used I would have left out but otherwise it seems fair.
The idea is interesting even though it probably needs to mature. It's interesting to see this kind of libraries popup though, there's clearly some kind of "backend - frontend split" fatigue going on.