Replies: 1 comment
-
Related discussion #11525 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First Check
Commit to Help
Example Code
Description
In #11503,
fastapi
now includes multiple dependencies that some users do not need.fastapi-slim
was introduced as a separate package without the automatic inclusion of those dependencies. This is fine for direct users offastapi
who can choose to install thefastapi-slim
package instead offastapi
, but this doesn't work for libraries that are non-optionally dependent on fastapi, such as https://github.com/dialoguemd/fastapi-sqla.Maintainers of such repos must choose between 3 approaches :
fastapi
, thereby removing the ability for those library users to usefastapi-slim
. Users technically could adopt fastapi-slim, but they would get 2 installations of the package, and would still get all dependencies.fastapi-slim
and force library users to switch to that. This is a breaking change given that users must change their direct requirement on fastapi, if they have it, so as to avoid a double installation of fastapi.Has anyone found a better workaround?
It seems to me like the approach that would make fastapi a better python citizen would be to revert back to using extras as intended : additional packages that enhance the functionality of the package, but aren't absolutely required.
Operating System
Linux, macOS
Operating System Details
No response
FastAPI Version
0.111.0
Pydantic Version
N/A
Python Version
N/A
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions