Replies: 2 comments 1 reply
-
Below codes are really bad... "langchain_community" or "langchain_core" or "langchain_openai", these are design details for the LangChain architecture... should not expose to "end user"/developers.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing the feedback. We realize that this is inconvenient for some users since it involves making changes in user code when upgrading langchain and being aware of more packages. We've shared some rationale for doing so here: There are a number of reasons why having the The conclusion was that it will make a better experience for users long term to know which packages are actually being used under the hood. Consider also that if the user is only working with OpenAI, it makes it much easier to find all the OpenAI related code since it lives in the OpenAI package. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For the end use, I mean, developers who are using langchain, it is difficult to "understand" which feature is in core, which is in community. Either the "community" or "core" are for contributors of LangChain, not for "users". From user's perspective, they are facing "prompts", "chaints" or "models", they don't need to care about community or core.
So, for the "users", they only need to: from
langchain.prompts import XXX
orfrom langchain.chains import blabla
, instead of they need to figure out from core or community.My thoughts
Beta Was this translation helpful? Give feedback.
All reactions