Files
langchain/libs
Mason Daugherty d3eb2296e7 fix(core): avoid dict shadowing in language models (#38480)
Fixes #37835

---

When Pydantic collects fields for a `BaseLanguageModel` subclass that
defines a `dict()` method, inherited annotations can resolve `dict`
against the subclass namespace instead of the builtin. With Pydantic
2.14.0a1 this caused `BaseLanguageModel.metadata: dict[str, Any] | None`
to fail during rebuild/import with `'function' object is not
subscriptable`.

This qualifies the inherited `metadata` field annotation as
`builtins.dict[...]`, matching the existing pattern in chat models, and
documents why the runtime import cannot move behind `TYPE_CHECKING`. It
also adds a regression test that rebuilds a `BaseLanguageModel` subclass
with a `dict()` method so core catches this failure before partner
packages hit it at import time.

Related to #37924, which hardens `_create_subset_model_v2`; this PR
fixes the `BaseLanguageModel` class-construction failure directly.
2026-06-26 03:14:47 -04:00
..
2026-06-26 02:46:31 -04:00

LangChain Monorepo

Important

Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.

Important

View all LangChain integrations packages

This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:

core/             # Core primitives and abstractions for langchain
langchain/        # langchain-classic
langchain_v1/     # langchain
partners/         # Certain third-party providers integrations (see below)
standard-tests/   # Standardized tests for integrations
text-splitters/   # Text splitter utilities

(Each package contains its own README.md file with specific details about that package.)

Integrations (partners/)

The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:

Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.

For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.