Live data from Hacker News

FastAPI 0.100.0 release notes

fastapi.tiangolo.com

111–115 of 115 posts

Re: FastAPI 0.100.0 release notes

#111

Earlier quoted context omitted.

No, they don't. They literally link out to semver.org

The joke . . . Your head

Yeah, really not though: you clearly haven't seen projects that actually use that as their official versioning policy ever since semver.org got published. So no, the joke didn't go over my head, because zerover stopped being a joke years ago. Unfortunately for everyone, the world took it seriously.

Do try to catch up.

Re: FastAPI 0.100.0 release notes

#112

I wish Django would take async more seriously. This comment gives a pretty good overview of the current situation (some points are more valid than others): https://github.com/encode/django-rest-framework/discussions/... The Python ecosystem is strange. Where other dev communities will embrace new ways of doing things faster than most people can keep up — the Python community needs to be pulled kicking and screaming i…

Have a look at Starlette, it’s by the guy who made Django. FastAPI is built on Starlette and adds more batteries included. If you’re interested in async you’re far better off to go async native than with a framework that’s synchronous. Asyncpg is the fastest Python Postgres driver there is, works well with sanic, Starlette or FastAPI.

The Starlette dev is the founder of Django Rest Framework.. Which is my least favorite part of working with Django. I really wish Django shipped with its own REST Framework.

I’ve been keeping an eye on FastAPI, Starlette, and a few other libraries but, compared to Django, they’re mostly powered by hype. I found a bunch of Pydantic bugs 2(3?)+ years ago that are only now getting addressed in v2.

Re: FastAPI 0.100.0 release notes

#113
post #98
post #94

Earlier quoted context omitted.

> This is simply not true. So sad. Ah sorry, so, just coincidentally pydantic happened to be slower than any other library that had a PR to be added to the benchmark, but that was not the reason they were rejected. Better now? > Please show me a sensible benchmark where your library is faster than pydantic? $ python3 perftest/realistic\ union\ of\ objects\ as\ namedtuple.py --pydantic (1.2192879340145737, 1.259595165…

¯\_(ツ)_/¯ - I get different results, see the PR.

It seems you're running on apple. I really can't reproduce since i don't own one, and unless I get it as a gift I never will.

Anyway no server code runs on apple, so it isn't that important to win benchmarks only on apple, I think.

Re: FastAPI 0.100.0 release notes

#114

Earlier quoted context omitted.

Have a look at Starlette, it’s by the guy who made Django. FastAPI is built on Starlette and adds more batteries included. If you’re interested in async you’re far better off to go async native than with a framework that’s synchronous. Asyncpg is the fastest Python Postgres driver there is, works well with sanic, Starlette or FastAPI.

The Starlette dev is the founder of Django Rest Framework.. Which is my least favorite part of working with Django. I really wish Django shipped with its own REST Framework. I’ve been keeping an eye on FastAPI, Starlette, and a few other libraries but, compared to Django, they’re mostly powered by hype. I found a bunch of Pydantic bugs 2(3?)+ years ago that are only now getting addressed in v2.

Django does come with it's own rest framework built in. Instead of rendering to templates, just return json.

Re: FastAPI 0.100.0 release notes

#115

Earlier quoted context omitted.

The Starlette dev is the founder of Django Rest Framework.. Which is my least favorite part of working with Django. I really wish Django shipped with its own REST Framework. I’ve been keeping an eye on FastAPI, Starlette, and a few other libraries but, compared to Django, they’re mostly powered by hype. I found a bunch of Pydantic bugs 2(3?)+ years ago that are only now getting addressed in v2.

Django does come with it's own rest framework built in. Instead of rendering to templates, just return json.

There are a lot of other things to consider. Django only supports GET and POST out of the box and Django forms aren’t serializers. Those are just the obvious ones. Just returning JSON isn’t practical.
Post reply on HN