Skip to content

Migrate to langchain >=0.1.0,<0.3 - #5

Open
ehsandaya1-blip wants to merge 1 commit into
sugarforever:mainfrom
ehsandaya1-blip:relay/langchain-0.1.0
Open

ehsandaya1-blip wants to merge 1 commit into
sugarforever:mainfrom
ehsandaya1-blip:relay/langchain-0.1.0

Conversation

@ehsandaya1-blip

Copy link
Copy Markdown

This updates the project's use of langchain from <0.1.0 to >=0.1.0,<0.3, following the provider's migration guide (https://python.langchain.com/docs/versions/v0_2/).

What changed

  • langchain.chat_models.ChatOpenAI / langchain.llms.OpenAI / langchain.embeddings.OpenAIEmbeddings (+ Azure variants)langchain_openai.{ChatOpenAI, OpenAI, OpenAIEmbeddings, AzureChatOpenAI, AzureOpenAI, AzureOpenAIEmbeddings} (32 sites): OpenAI integrations moved to the langchain-openai partner package.
  • langchain.{vectorstores,document_loaders,utilities,tools,retrievers,chat_models,llms,embeddings,docstore,graphs,storage,agent_toolkits}.* → langchain_community.<same path> (18 sites): Third-party integrations moved to langchain-community with identical module paths.
  • langchain.text_splitterlangchain_text_splitters (8 sites): Text splitters moved to their own package (0.2).

Files touched: 28; files the mechanical pass matched but did not need to change: 2.

How this was produced

Deterministic rewrites from a machine-readable MigrationSpec for this upgrade, then a review pass on the semantic residue; every changed file was parsed and checked with pyflakes for new undefined names before this PR was prepared. No behaviour beyond the migration was touched: no reformatting, no import reordering, no unrelated code.

Happy to adjust anything — if the project deliberately pins the old major version, say so and I will close this.

Notes for reviewers

  • Three from langchain.schema.runnable import ..., Input lines became two imports each: the exported names from langchain_core.runnables plus from langchain_core.runnables.utils import Input (Input is not re-exported from the package root).
  • langchain.prompts, langchain.chains, langchain.tools, langchain.callbacks, langchain.load.serializable and from langchain import OpenAI still resolve in 0.1/0.2 and were left alone.

- **langchain.chat_models.ChatOpenAI / langchain.llms.OpenAI / langchain.embeddings.OpenAIEmbeddings (+ Azure variants)** → `langchain_openai.{ChatOpenAI, OpenAI, OpenAIEmbeddings, AzureChatOpenAI, AzureOpenAI, AzureOpenAIEmbeddings}` (32 sites): OpenAI integrations moved to the langchain-openai partner package.
- **langchain.{vectorstores,document_loaders,utilities,tools,retrievers,chat_models,llms,embeddings,docstore,graphs,storage,agent_toolkits}.*** → `langchain_community.<same path>` (18 sites): Third-party integrations moved to langchain-community with identical module paths.
- **langchain.text_splitter** → `langchain_text_splitters` (8 sites): Text splitters moved to their own package (0.2).
Files touched: 28; files the mechanical pass matched but did not need to change: 2.
Deterministic rewrites from a machine-readable MigrationSpec for this upgrade, then a review pass on the semantic residue; every changed file was parsed and checked with pyflakes for new undefined names before this PR was prepared. No behaviour beyond the migration was touched: no reformatting, no import reordering, no unrelated code.
Happy to adjust anything — if the project deliberately pins the old major version, say so and I will close this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant