test_remove_handler() — langchain Function Reference
Architecture documentation for the test_remove_handler() function in test_sync_callback_manager.py from the langchain codebase.
Entity Profile
Dependency Diagram
graph TD 0967c3ba_2e37_2790_64f1_3abdfcf4d02d["test_remove_handler()"] 748ec2b4_9c22_8e40_5174_c4bd290fcb4d["test_sync_callback_manager.py"] 0967c3ba_2e37_2790_64f1_3abdfcf4d02d -->|defined in| 748ec2b4_9c22_8e40_5174_c4bd290fcb4d style 0967c3ba_2e37_2790_64f1_3abdfcf4d02d fill:#6366f1,stroke:#818cf8,color:#fff
Relationship Graph
Source Code
libs/core/tests/unit_tests/callbacks/test_sync_callback_manager.py lines 4–15
def test_remove_handler() -> None:
"""Test removing handler does not raise an error on removal.
An handler can be inheritable or not. This test checks that
removing a handler does not raise an error if the handler
is not inheritable.
"""
handler1 = BaseCallbackHandler()
handler2 = BaseCallbackHandler()
manager = BaseCallbackManager([handler1], inheritable_handlers=[handler2])
manager.remove_handler(handler1)
manager.remove_handler(handler2)
Domain
Subdomains
Source
Frequently Asked Questions
What does test_remove_handler() do?
test_remove_handler() is a function in the langchain codebase, defined in libs/core/tests/unit_tests/callbacks/test_sync_callback_manager.py.
Where is test_remove_handler() defined?
test_remove_handler() is defined in libs/core/tests/unit_tests/callbacks/test_sync_callback_manager.py at line 4.
Analyze Your Own Codebase
Get architecture documentation, dependency graphs, and domain analysis for your codebase in minutes.
Try Supermodel Free