From b58d492e05ddc63b2c9c433ad516f58699044d91 Mon Sep 17 00:00:00 2001 From: NavanitDubeyShorthillsAI <142497828+NavanitDubeyShorthillsAI@users.noreply.github.com> Date: Sat, 19 Aug 2023 01:33:15 +0530 Subject: [PATCH] Update pydantic_compatibility.md (#9382) Co-authored-by: Eugene Yurtsev --- docs/extras/guides/pydantic_compatibility.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/extras/guides/pydantic_compatibility.md b/docs/extras/guides/pydantic_compatibility.md index 15518c5e23e..4d98adaec67 100644 --- a/docs/extras/guides/pydantic_compatibility.md +++ b/docs/extras/guides/pydantic_compatibility.md @@ -7,14 +7,14 @@ ## LangChain Pydantic Migration Plan -Langchain will carry out the migration to pydantic v2 in two steps: +LangChain will carry out the migration to pydantic v2 in two steps: 1. 2023-08-17: LangChain will allow users to install either Pydantic V1 or V2. * Internally LangChain will continue to [use V1](https://docs.pydantic.dev/latest/migration/#continue-using-pydantic-v1-features). * During this time, users can pin their pydantic version to v1 to avoid breaking changes, or start a partial migration using pydantic v2 throughout their code, but avoiding mixing v1 and v2 code for LangChain (see below). -2. 2023-08-25: Langchain will migrate internally to using V2 code. +2. 2023-08-25: LangChain will migrate internally to using V2 code. * Users will have to upgrade to V2 as well to use LangChain. * Users should stop using the `pydantic.v1` namespace when using LangChain. * See the [bump-pydantic package](https://github.com/pydantic/bump-pydantic) to help with the upgrade process.