Move _openai_function_dict and _openai_function_chars from manual __dict__ stashing in external functions to proper cached_property declarations on ChildTool, consistent with how tool_call_schema and args are already cached. Extract _compute_openai_function_dict (pure computation, no caching) from _format_tool_to_openai_function so ChildTool._openai_function_dict can call it without circular dependency. _format_tool_to_openai_function now delegates to tool._openai_function_dict for ChildTool instances and falls back to direct computation for other BaseTool subclasses. _openai_function_chars chains off _openai_function_dict so json.dumps is also computed at most once per mutation cycle. count_tokens_approximately accesses tool._openai_function_chars directly instead of managing __dict__ by hand. Invalidation via ChildTool.__setattr__ (popping both keys on args_schema / description / name mutation) is unchanged.
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
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.