-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Add FastAPI CLI, the new fastapi
command
#11522
Conversation
📝 Docs preview for commit c98c151 at: https://a98e0cab.fastapitiangolo.pages.dev |
fastapi
commandfastapi
command
So now my servers will depend on some CLI packages? 🤔 |
Thanks for this great feature. It also would be nice to support module's |
Why do we need it for production? Could you make it optional dependency? |
Thanks for this functionality, it really is great. fastapi fan. @tiangolo 🏆 |
See fastapi/fastapi#11522 for details
See fastapi/fastapi#11522 for details
Really, why, of all the things... |
I think you still available to run |
@parfeniukink poetry doesn't, besides, I don't want to manage dependencies myself. I'm migrating over to Litestar, it has more than one maintainer. |
Good choice I guess :) |
We'll see ;) |
@tiangolo I understand fastapi cli is running uvicorn under the hood. |
@tiangolo a few comments:
However:
Personally I think it's a decent feature (and, on par with FastAPI's high standards, it appears to be thoroughly tested and clearly documented). It will probably help out FastAPI newcomers the most, with a friendlier getting-started experience. I don't need it urgently, not sure if I'll use it, I might give it a try. Anyway, what the feature is that you built, isn't the point here. In future, could you at least leave a PR (for a non-critical new feature) open for a reasonable time, before merging it? I would suggest one week, to give people some time to review and comment. And ideally, could you advise the community in advance, in a separate issue thread, and/or in the roadmap, of features that you plan to work on? I'm not suggesting a radical overhaul of how the project is managed. I just think that a little bit more transparency, and a little bit more engagement, are not unreasonable expectations of the community, for a project that thousands of people now rely on. And I don't want to see people abandon FastAPI on account of these concerns (as some of the comments in this PR have suggested, and as I've seen suggested in a number of discussions elsewhere), I think it's a great project, and I'm saying all this in the hope that it helps rather than harms the project's future. |
Thanks for the feedback @Jaza and everyone! As having So, to get the standard optional dependencies people now have to install it with: pip install "fastapi[standard]" Note: remember to use the quotes, depending on your terminal that might be required. Having the optional extra, square brackets, quotes, is not as nice as just This is available in FastAPI version 0.112.0. 🎉 |
Moreover `fastapi-slim` itself is discontinued from maintainers see fastapi/fastapi#11522 (comment) see https://fastapi.tiangolo.com/release-notes/#01120
Moreover `fastapi-slim` itself is discontinued from maintainers see fastapi/fastapi#11522 (comment) see https://fastapi.tiangolo.com/release-notes/#01120
Moreover `fastapi-slim` itself is discontinued from maintainers see fastapi/fastapi#11522 (comment) see https://fastapi.tiangolo.com/release-notes/#01120
Moreover `fastapi-slim` itself is discontinued from maintainers see fastapi/fastapi#11522 (comment) see https://fastapi.tiangolo.com/release-notes/#01120
✨ Add FastAPI CLI, the new
fastapi
command