## Description Fixes #33453 `ModelResponse` was defined in `types.py` and included in its `__all__` list, but was not exported from the middleware package's `__init__.py`. This caused `ImportError` when attempting to import it directly from `langchain.agents.middleware`, despite being documented as a public export. ## Changes - Added `ModelResponse` to the import statement in `langchain/agents/middleware/__init__.py` - Added `ModelResponse` to the `__all__` list in `langchain/agents/middleware/__init__.py` - Added comprehensive unit tests in `test_imports.py` to verify the import works correctly ## Issue The original issue reported that the following import failed: ```python from langchain.agents.middleware import ModelResponse # ImportError: cannot import name 'ModelResponse' from 'langchain.agents.middleware' The workaround was to import from the submodule: from langchain.agents.middleware.types import ModelResponse # Workaround Solution After this fix, ModelResponse can be imported directly as documented: from langchain.agents.middleware import ModelResponse # Now works! Testing - ✅ Added 3 unit tests in tests/unit_tests/agents/middleware/test_imports.py - ✅ All tests pass locally: make format, make lint, make test - ✅ Verified ModelResponse is properly exported and importable - ✅ Verified ModelResponse appears in __all__ list Dependencies None. This is a simple export fix with no new dependencies. --------- Co-authored-by: Eugene Yurtsev <eugene@langchain.dev> Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com>
Packages
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.