Jinja2 VS starlette

But, on the other hand, I can read in the jinja repository that there is not the same Switching From Other Template Engines and also exists documentation about Support for templates engines

jinja: Default templating engine for and dependency of flask

or as complex as bringing Jinja into the picture. Some other options include mustache templates, the built in Template class, and some libraries noted here.

Jinja

- Link: https://github.com/pallets/jinja/blob/master/jinja2/sandbox.py

Cookiecutter is a command-line utility that creates projects from templates. There's a list of templates maintained by the cookiecutter team and plenty of community awesome lists. It's built with python and uses the jinja templating framework (found in python web frameworks like flask). You can use it to make a template for pretty much anything! All you need to get started is pip install cookiecutter.

This major release of Flask is accompanied by major releases of Werkzeug, Jinja2, click, and itsdangerous which we'd also welcome and appreciate testing (their pre releases are installed with the Flask pre release).

So I went back to boring technology. I took Jinja2 and rendered html from the template. The code has almost halved, and rationality has doubled.

Fast Execution: FastAPI is built on top of Starlette and Pydantic, making it one of the fastest Python frameworks for building APIs.

The framework's efficiency comes from its use of Starlette for building asynchronous web services and Pydantic for robust data validation and serialization, powered by Python's type hints. Pydantic has recently announced the official release of Pydantic V2 (June 2023), which is a ground-up rewrite that offers many new features and performance improvements, so make sure to be using that instead of V1.

Uvicorn + Starlette 8k requests/s

Starlette documentation

Same here, but without these weird utils it doesn't get any better.

I have 7 YoE with Django. Its great at so many things. You see some code, like middlewares, and immediately understand what's going on.

Now, we also have Starlette. The base of all new, fancy asgi libraries. Here's the base middleware class.

https://github.com/encode/starlette/blob/8d7a1cacfb3e1a30cbb...

In the last couple of years I heard 'we're running fastapi on production. Wanna join us?' so many times... but the reality is that it's still not suitable for prod. Who wants to work with a code like that if you have a readable, stable Django? I'm clueless.

Correct. Yeah I’ve been trying to find stuff. It often circles back to the issue I linked (https://github.com/encode/starlette/issues/1724)

In this thread, starlette people admitting they don’t have anywhere near the tuning features necessary for more heavily sync oriented people https://github.com/encode/starlette/issues/1724

Perhaps you are thinking about Starlette, the toolkit Starlite was originally based on? But Starlette as well won't have an influence on FastAPI's Pydantic dependencies, since Starlette never dependent on Pydantic in the first place.