3 ms·
Exactly. FastAPI's maintainer was so unprepared he had to stir up a storm to prevent a legitimate Python feature from coming in. One of the benefits of a larger
by bobthebuilders 5y ago
Exactly. FastAPI's maintainer was so unprepared he had to stir up a storm to prevent a legitimate Python feature from coming in. One of the benefits of a larger and more involved community process is the fact that each person exerts less individual control.
- stavros 5y agoHmm, what's the context there? I'm not familiar with the FastAPI events you mention.
- bobthebuilders 5y agoThey threatened the Python language committee if they didn't get their way wrt PEP 576. Their library also contains C extensions with undefined behavior, and telemetry that phones home.
- adamzegelin 5y ago> Their library also contains C extensions with undefined behavior, and telemetry that phones home. Source for this?
- bobthebuilders 5y agoMy bad, I was confused with another project. I can't edit it now.
- hluska 5y agoThis is a really classy reply. Nice job! We all muck things up but it takes a special person to admit to it. :)
- jsmeaton 5y agoWow this is a really uncharitable interpretation of what happened.
- stevesimmons 5y agoI don't think your choice of language helps here. The reference to PEP576 here relates to some changes to annotations/type hints originally planned for Python 3.10. For anyone interested, here is a great summary from Linux Weekly News two weeks ago: https://lwn.net/Articles/858576/ https://lwn.net/Articles/858576/
- jt_b 5y agoYeah, going to need to see some evidence and source code references for allegations like this.
- svaha1728 5y agoNah... That's not what happened. Please read Sebastián Ramírez's post on the issue: https://dev.to/tiangolo/the-future-of-fastapi-and-pydantic-is-bright-3pbm https://dev.to/tiangolo/the-future-of-fastapi-and-pydantic-i...