Сейчас в эфире @tiangolo
С темой: Intro to FastAPI

Во время доклада отмечайте спикера и задавайте вопросы в этом чате на английском, он вам ответит.

Вопросы на русском также можно писать, их модератор задаст в прямом эфире после доклада.

Если хотите задать вопрос лично в эфире, проверяйте свою камеру и гарнитуру и пишите мне в личку :)

Рамирас создатель мема )

"pls, no xml"- 😭 you don't like SOAP?!:)) why?!))

I like this one more

😭 I think I don't have good memories with SOAP 🧼 😂

)))

I ❤️ WSDL

Ah! That's in Spanish, it says more or less "Sebastián Ramírez has a cum laude preschool diploma"

...I'm kidding, it's not cum laude 😔

about OpenAPI - FastAPI support it totally or some limitations?

An application build with FastAPI will be compatible with OpenAPI, yes. And most of the things that can be defined with OpenAPI can be defined in code with FastAPI. OpenAPI has some special cases that are not necessarily easy to generate automatically, but most of it yes.

@tiangolo about FastAPI when migrate some project, for example, from Flask, how important to change all sync stuff from sync to async? how it can side project? I mean of course not computations, but some i/o sync operations, for example, if in a lot of places in project used 'requests 'library'?

at the end we already will change all sync to async, but can we go to prod with 'partial' migration?

Doctor Strange
Is it possible to use BaseModel-based classes as return values, i.e. return something like Result(message='...', ...) instead of {'message': ...}?

Also, OpenAPI is based on JSON Schema, the currently published version, 3.0.3 is based on an older version of JSON Schema that has a couple of small differences with the latest versions of JSON Schema. The latest RC version of OpenAPI, 3.1.0, is built on the latest JSON Schema version.

FastAPI is built on Pydantic, that generates JSON Schema with the latest versions. So, the OpenAPI generated by FastAPI has some differences in a couple of corner cases where it is compatible with the latest RC version of OpenAPI. The advantage is that the internal JSON Schema declarations use the latest version, that are compatible with recent tools that use them, e.g. automatic frontend components.

got it

and thanks :)

Yes, exactly, when you use a normal def function definition, FastAPI will run it on a threadpool to not block the event loop. So, it will do the "sensible" thing. You can easily keep mostly the same code and then optimize only the "routes"/"path operations" that you need to have extra concurrency/performance.

Good question! Yes, you can. In fact, you can also declare the response_model to use for that path operation and it will be documented in the automatic UI. And you can use Pydantic's orm_mode to declare the model to use for the response and even return an arbitrary object, like an ORM object (e.g. SQLAlchemy). But sure, yes, you can return BaseModel responses directly.